Enterprise
Run Brindola under your own brand, inside your own stack.
For groups and software companies
Enterprise is for restaurant groups, hospitality companies and software companies that already operate their own backoffice. The skin system carries the product's name, wordmark, colours and defaults, so your deployment is a configuration and an asset set rather than a fork you have to keep merging. One hospitality group already runs it this way.
Your backoffice behind it
Connect your backoffice through Brindola's published protocol. Venue settings, catalog and staff come down; daily sales totals go up. Each venue keeps its own records, with its terminals sharing one connection. Your backoffice brings the locations together.
Central purchasing, in development
Local supplier orders and receiving are available now. We are building central purchasing around requests from each venue, approved orders allocated to their destinations and deliveries recorded where the goods arrive. Supplier invoices and payments stay separate, so receiving a delivery never marks a bill paid. A hosted Brindola backoffice is a future option; it is not available to subscribe to today.
Your market's rules, as a package
Fiscal drivers, order intake, identifier rules and invoicing all sit behind interfaces, so a new country is a package and a configuration row rather than a branch in somebody's cashier screen.
Delivery platforms, already connected
Your venues receive orders from the delivery platforms live in their market through our integrator registration and multi-tenant order bridge, with no separate platform integration to build or maintain on your side. Each region's delivery page names the platforms connected there.
An architecture that holds up
Every venue keeps trading through an outage, and every venue's data stays in its own building. Nothing on the ordering, kitchen or payment path depends on a connection you do not control.
One contract
Enterprise is priced per contract: device counts, support and the integration work, agreed once. No revenue share, in either direction.
What an integration actually takes
- A skin with the name, wordmark, colours, defaults and the strings your market expects, which takes days rather than months.
- A backoffice endpoint implementing Brindola’s published protocol, checked with its conformance suite.
- A country package if your market needs one: the fiscal driver, the identifier rules, the invoicing lane.
- A pilot venue, run end to end against your backoffice, before anything is signed.
Tell us about your stack
Bring us your backoffice, your market and the venues you run, and we will tell you within a week what the integration looks like and what it costs. One address and one person, with no discovery-call funnel.