Build the frontend your team needs. Keep the platform underneath managed.
The frontend source code of the web storefront, customer apps, Merchant App, and Driver App is open source and included with every Ordering.co product, so your team can build on the technology that already runs the platform and choose its own release process. By default, the backend and the Ordering.co API are managed by Ordering.co. Enterprise organizations can license the backend source code under a separate agreement, subject to approval.
What is open source
Four frontends, in source.
- 01
Ordering Web storefront
Frontend code for the web ordering surface, including the customer-facing journey from menu to account and order tracking. - 02
Customer apps
Frontend code for the customer applications used to browse, order, and follow an order. - 03
Merchant App
Frontend code for the tools stores use as they accept, prepare, and track orders. - 04
Driver App
Frontend code for the app drivers use to receive assignments and complete deliveries.
The backend is on us
Build the frontend. Leave the backend to Ordering.co.
Your engineers spend their time on the experience customers see. Ordering.co runs, secures, scales, and maintains the backend and the Ordering.co API underneath it, on the technology that has powered ordering operations since 2012.
Managed infrastructure is included in every plan. This description does not establish an SLA or a specific certification.
- No servers to run
- Ordering.co operates the managed AWS infrastructure for you, so your team has no backend servers to maintain.
- Scales with your orders
- Auto-scaling infrastructure built to process millions of orders a month.
- Secure by design
- Encrypted data transmission, access controls, continuous monitoring, and backups.
- High availability
- A high-availability architecture, distributed globally to support reliable performance.
- Proven with enterprise
- Technology proven with enterprise companies and refined since 2012.
- API and MCP included
- Build on the Ordering.co API and connect compatible AI tools through MCP, while Ordering.co keeps them running.
Run Ordering.co in your own cloud.
Enterprise packages install Ordering.co in your AWS, Google Cloud, Microsoft Azure, or Railway account.
- The whole backend: API, webhooks, and real-time.
- One contract at a fixed rate, with no charges per store or by transaction volume.
What stays managed
The frontend is open source. The backend is managed by default.
The boundary is clear: your team works on the open source frontend code, while Ordering.co manages the backend and the Ordering.co API by default. That keeps the question practical: which customer and operator surfaces does your team want to change?
Backend and API
By default, the backend and the Ordering.co API are managed by Ordering.co. The backend source code is available only to enterprise organizations, under a separate license agreement and after Ordering.co approves the organization.
Platform services
The services behind the frontend remain part of the managed platform rather than code your team receives.
Your frontend release process
Your team decides how it changes and releases its frontend code. The managed backend remains outside that release process.
An intentional boundary
Open source frontend code does not transfer ownership of the platform, backend, or API. It gives your team a defined frontend surface to evolve.
How it works
Start with the surfaces your team wants to evolve.
Working from the frontend source code is a fit when the standard interface needs deeper work from your engineers. Start with the surfaces in scope and the boundary between that code and the managed platform.
- 01Choose the surfaces in scopeThe frontend source code comes with every Ordering.co product. Decide which web, customer, merchant, or driver surfaces your team will take on.
- 02Work from the open source frontendYour engineers use the frontend code as the starting point for the interface they are responsible for.
- 03Build your own UX and featuresUse the frontend code as the place to adapt interface flows, presentation, and components to your product requirements.
- 04Define the release boundaryDecide how your team will maintain and release its frontend alongside the managed platform services it connects to.
- 05Keep the platform boundary clearThe managed backend and the Ordering.co API remain with Ordering.co. Align the frontend work with that boundary as your team designs the implementation.
Which route
Choose the level of frontend involvement.
Configuration, frontend source code, and custom work are different ways to approach the interface. The useful distinction is who changes and maintains the frontend.
- 01White labelStart from configured surfaces when your team needs a branded ordering experience without taking on frontend source code.
- 02
Frontend source code
Work from the open source frontend when your engineers want a defined surface to adapt and maintain, with the backend and API still managed. - 03Custom projectsUse custom work when the interface or integration needs a project designed around your particular requirements.
Questions
Questions about the source code.
Which products include the frontend source code?
Every Ordering.co product. The frontend source code is open source, so your team can build on the technology that already runs the platform.
Is the backend included?
No. The open source code is the frontend: the web storefront, the customer apps, the Merchant App, and the Driver App. By default, the backend and the Ordering.co API are managed by Ordering.co. The backend source code is available only to enterprise organizations, under a separate license agreement and after Ordering.co approves the organization.
How does a team get the code and start working locally?
Open the product in the Builder and download the frontend source code as an archive. Unzip it, open the folder in your terminal, and start a local server to preview changes as your team works, before deciding where the built frontend will run.
Can we run Ordering.co in our own cloud?
Yes, with an enterprise package. Ordering.co can be installed in your AWS, Google Cloud, Microsoft Azure, or Railway account. Every other plan runs on the managed infrastructure that Ordering.co operates for you.
Who maintains the code my team changes?
Your team maintains and releases the frontend code it changes, with its own release process. Ordering.co continues to run the backend and the API that frontend connects to.
Can we adapt the frontend for specific devices, browsers, or integrations?
Yes. Working from the frontend source code lets your team optimize the interface for the devices and browsers your customers use and add the integrations your product needs, such as analytics or other external tools, while the backend and the Ordering.co API stay managed by Ordering.co.
Define the frontend boundary before you build.
Tell us which web, customer, merchant, or driver surface your team wants to evolve. We can walk through what the frontend source code covers and what remains managed.