Protect the build
Start from established catalogue, order, refund, customer, and payment behavior.
Engine only
Build commerce services from a complete API foundation.
For institutions with product and engineering teams ready to own every merchant and customer-facing surface, use the domain model behind Box without taking a prebuilt interface.
Run it locally
Why Engine Only
Keep the commerce domain. Own the experience.
Set clear boundaries
Generate against the exact installed package set, with unavailable endpoints absent from the contract.
Keep control
Own every interface and bind external providers through explicit ports.
How it works
Move from installed packages to an interface you own.
The deployment generates its contract from what is installed. Your team builds against that contract, then connects the providers it has approved.
Start with the model
Load the licensed packages.
Products, websites, checkouts, payments, orders, customers, and transactions form one consistent model.
Describe the deployment
Generate your OpenAPI document.
The contract reflects what is actually installed rather than every capability the platform could provide.
Build the interface
Create clients against your own host.
Your developers work from the contract produced by the deployment they are integrating with.
Operate safely
Bind providers when you are ready.
Payment, messaging, and settlement ports do nothing until an operator supplies an approved implementation.
Technical resources
Local testing
Bring up the stack and exercise workflows before connecting production services.
Read the guide →API reference
Understand the commerce resources and operations exposed by your deployment.
Read the guide →Generated clients
Create typed clients from the OpenAPI document served by your own box.
Read the guide →Authentication
Bind the engine to the institution’s identity boundary.
Read the guide →Deployment
Operate Box in the environment and region you choose.
Explore →Security model
Review boundaries, data ownership, identity, and provider connections.
Explore →Frequently asked questions
Can we use our own authentication?
Yes. The engine binds to the institution’s authentication guard.
Can we choose our payment provider?
Yes. Payment capability is connected through an implementation supplied by the operator.
Are unavailable features hidden?
They are absent from the deployed API rather than exposed and rejected at runtime.
Can we add surfaces later?
Yes. Embedded components and full surfaces are packages added to the same deployment.
Where does the data live?
Inside the infrastructure and region operated by the institution.
How are upgrades handled?
The institution chooses when to install licensed package updates.
Ready to work against your own Box?
Run the platform locally, inspect its API description, and decide how much of the experience your team wants to build.
Start locally