Cibuscibus.
Platform overview

The connected operating layer for modern restaurants.

Cibus connects front-of-house, kitchen, payments, staff, reporting, customer engagement and delivery into one restaurant system, with configured surfaces using connected menu, order, payment and customer context.

One live operating layer for service, kitchen, payments, staff, customers, growth and delivery.

Book a DemoSee how Cibus works
Cibus operating layer
Connected restaurant system
Live
Core data layer
Connected records
Menu
Orders
Payments
Customers
Staff
Reports
Connected surfaces
POSQR Order & PayKitchen DisplayStaff MobileAdmin DashboardStorefrontReachStoriesRiderAI InsightsSales Agent Portal
One operating layer

Six connected truths.

Cibus uses shared identifiers and connected records so each configured surface can read the operational context relevant to its workflow. Product, provider and market boundaries still apply.

Connected menu across configured channels
POS · QR · Storefront · Rider · KDS

Maintain shared menu records for configured POS, QR, Storefront, Rider and KDS workflows, with supported local or channel differences.

CategoriesModifiersAllergensAvailability
One order flow
Table · Counter · QR · Online · Delivery

Supported order sources use connected identifiers and order context from creation through fulfilment and reporting.

Order openItems addedSent to kitchenClosed
One kitchen queue
KDS stations · Expediter · Staff Mobile

Tickets route by station and move through claim, prep, bump and serve in real time.

RoutedClaimedIn prepReady
Connected payment and receipt records
Stripe · Terminal · Cash · Splits · Tips

Supported payment allocations remain associated with the relevant order, with totals calculated in minor units.

CapturedTip appliedSplitReceipt issued
Connected customer context
Storefront · Reach · Stories · AI Insights

Identified, authorised order, preference and consent records can inform Reach, Stories and Insights workflows.

ProfileConsentSegmentsHistory
One management workspace
Admin · Reports · Locations · Roles

Authorised owners and managers can work with configured menus, staff, payments and locations from the Admin workspace.

TodaySalesMenuLocations
End-to-end flow

From scan to kitchen to payment to insight.

Supported order and status events connect the configured Cibus ordering, kitchen, payment and reporting workflow. External providers, exceptions and offline conditions still follow their documented hand-offs.

  1. 01
    Order entry
    QR scan, online order, or staff entry at POS.
  2. 02
    Calculation
    Menu, modifiers, taxes and service charges from one source.
  3. 03
    Kitchen routing
    Tickets routed to the right stations on KDS.
  4. 04
    Live status
    Staff and customers see order progress update.
  5. 05
    Payment
    Stripe, Terminal, wallet, cash or split payment captured.
  6. 06
    Receipt
    Receipt issued and tied to the order line.
  7. 07
    Insight
    Reports, AI Insights, Reach and Stories use the operational data.
Product surface map

Every surface has a role.

Real-time operations layer

Supported status updates across service.

While connected, supported order, ticket, table and payment-status events update the relevant configured Cibus views. Service, kitchen and management see the state their role and workflow permit.

Order placedTicket routedPayment confirmedReceipt issuedDashboard updated
Realtime event stream
Live across connected surfaces
Streaming
  • Order placed
    just now
  • Ticket routed
    just now
  • Claimed at station
    just now
  • Ready for pass
    just now
  • Payment confirmed
    just now
  • Receipt issued
    just now
  • Dashboard updated
    just now
Money & control layer

Payments and receipts connected to orders, with totals calculated in minor units.

Cibus calculates money in integer cents and records payments through defined order workflows. Restaurants can review how line items, taxes, charges, discounts and payment allocations form each total.

Exact-cent calculation engine
Tax, discount and service-charge math done in integer cents.
Taxes, discounts, service charges & tips
Applied consistently across in-venue and online channels.
Stripe & Stripe Terminal
Card-not-present and card-present captured against the same order.
Cash and manual card recording
Recorded with attribution to the staff member and shift.
Split payments
Multiple methods on one order with balanced totals.
Receipts
Supported receipt paths are linked to the relevant order and payment record.
EOD reconciliation
Daily close that ties payments to orders and float.
Payment records
Payments and allocations are recorded against the relevant order.
Roles, permissions & tenant isolation

Built for teams, locations and scoped access.

Cibus is designed so the right people see the right data — across staff, managers, owners, partners and multi-location groups.

Staff roles and permissions
Role-based access for managers, servers, kitchen and counter staff.
Capability-aware access
Sensitive actions like refunds or menu changes are scoped to the right roles.
Sales agent scoped portfolio access
Scoped access restricts partners to restaurants assigned to their portfolio.
Multi-location operators
Location-level configuration with group-level oversight.
Restaurant-level tenant isolation
Database policies enforce restaurant scope on tenant data.
Secure access patterns
Authenticated access is scoped through platform roles and database policies.
Multi-location & partner layer

Start with one site; manage additional locations on the same operating layer.

Cibus supports independent restaurants, multi-location groups and sales-agent-led onboarding with location-specific settings and scoped group oversight.

Multi-location management
Location-specific settings with group-level oversight and reporting.
Explore →
Sales Agent Portal
Partner workspace for onboarding restaurants and tracking portfolios.
Explore →
Admin Dashboard
Operational controls and roles per location.
Explore →
Pricing
Commercial model shaped around your operation and rollout.
Explore →
Go deeper

Explore the platform.

How Cibus worksReal-time operationsPayments & moneySecurity & complianceMulti-location managementCompare Cibus
FAQ

About the Cibus platform.

Is Cibus one platform or separate apps?

Cibus is one connected platform with multiple surfaces for different restaurant users: owners, staff, kitchen teams, customers, riders and sales partners.

Run, grow and deliver from one operating layer.

See how Cibus connects service, kitchen operations, payments, reporting, customer engagement and delivery into one restaurant operating system.

Book a DemoSee how Cibus works