About Fortune OS
Fortune OS is a hospitality operating system: one application that covers the point of sale, the kitchen, the menu, the tables, the staff and the numbers of a restaurant or café, and that opens the same business data to the AI agents merchants already use.
What we build
Most venues run their business across a till, a kitchen screen, a menu tool, a booking sheet and a spreadsheet, and none of them agree with each other. Fortune OS replaces that set with one system of record. An order taken at the till becomes a kitchen ticket, a guest bill, an invoice and a line in the sales report without being re-entered, and a menu change in the catalog reaches the till, the QR menu and the kitchen at once.
The product is built for the Gulf and the wider region first: prices in the venue's currency, Arabic alongside English and Russian with right-to-left layout, VAT on every printed document, and payment terminals and gateways used there. Nothing in it is limited to that region.
Who builds it
Fortune OS is developed by the Fortis team, the people behind the Fortis point-of-sale platform. Merchants on Fortis move to Fortune OS with their catalog, order history, payments and people imported, and both products share one sign-in. The application, its desktop shells and its agent platform are engineered in one open monorepo of standards-driven code, and every rule the product follows is written down before it is enforced.
How the product is run
- Every page is rendered on the server, so a document is complete before any script runs and stays readable to a crawler or an agent.
- Application data is stored in the European Union, in the Frankfurt region, with production backups.
- Errors are reported to an error-tracking service hosted in the European Union, with personal data scrubbed before it leaves the application.
- Billing is handled by Stripe; Fortune OS never stores card numbers.
- AI agents authenticate with revocable API keys or OAuth, act only within the memberships and permissions the account already holds, and every business call is authorized again live.
Where to go next
Read the developer documentation for the API and MCP server, the contact page for how to reach the team, and the privacy notice for how data is handled. Agents start from llms.txt.