No. POS is one of the products inside the operating layer, alongside QR, KDS, Storefront, Reach, Rider, AI Insights and more.

Independent restaurants, cafés, bakeries, takeaways, casual dining, fine dining and multi-location restaurant groups.

Where is Cibus available?

The first localized commercial market is the United Kingdom, followed by Malaysia. Other countries use the global enquiry route until their product, payments, legal and support scope is confirmed during discovery.

Do you work with sales partners?

Yes. The Sales Agent Portal supports partners and resellers managing portfolios of restaurants.

Who owns the customer data?

The answer depends on the data and workflow. Restaurant operational data, diner personal data and website enquiries have different controller, processor, access and retention rules. Cibus confirms those responsibilities in the applicable agreement and privacy notice rather than using a blanket ownership claim.

How do we get started?

Book a demo. We'll walk through Cibus on your service flow and recommend the right modules for your operation.

About

A restaurant technology company built around the whole shift.

Cibus connects POS, QR ordering, kitchen, payments, staff, reporting, customer engagement and delivery, so restaurant teams can work from one operating context instead of a stitched stack.

Book a Demo Explore the platform

Cibus operating layer

Illustrative

Core

Connected menu · order context · supported events

Run

POSKDSQRStaffAdminPayments

Grow

StorefrontReachStories

Deliver

Rider

Intelligence

AI Insights

Partner

Sales Agent Portal

One restaurant · one platform · every shift

Positioning

Cibus is the restaurant operating system for every shift.

Cibus is a B2B platform, not a POS-only product or consumer food-delivery marketplace. Its web and mobile products use connected records, shared identifiers and supported events across configured service, payment, kitchen, customer-engagement and delivery workflows.

The pain we're solving

What restaurants put up with today

Several tools, one restaurant

POS, online ordering, customer marketing and delivery often sit in separate systems with separate records.

Staff retyping data

Menus, prices, customer details and order updates get rekeyed between systems that don't share a database.

Reports that don't agree

Different tools can use different definitions and cut-off times, leaving teams to reconcile the shift manually.

Customer context is fragmented

QR, online, phone and walk-in activity can be difficult to connect when each channel holds a separate record.

Customer activity is separated from outreach

Campaign planning is harder when consent and order context must be moved between systems.

Growth tools bolted on

Each new product (ordering, delivery, content) bolted onto a stack that wasn't designed for it.

Old way vs. Cibus

From separate tools to one operating layer

Stitched stack

POS, ordering, KDS, payments, marketing and delivery from separate vendors
Staff retype information between tools
Reports built in spreadsheets
Customer identity fragmented across surfaces
Each new growth tool added as a separate login

With Cibus

One operating layer connecting orders across the shift
Supported operational events connecting configured POS, KDS, payment, Storefront, Reach, Rider and Insights workflows
Operational reporting and reconciliation from connected records
Customer context connected across QR, Storefront and delivery workflows
Storefront, Reach, Stories and Rider live as native modules — not bolt-ons

What we believe

The principles behind the platform

•

Operator-first

Product decisions start with restaurant workflows: tables, tickets, kitchen stations, shifts, payments and hand-offs.

•

Restaurant-native vocabulary

Tables, tickets, passes, splits, service charges, shifts — not generic SaaS language.

•

Owner-reviewed AI

AI Insights and Stories surface recommendations and drafts. The owner decides. No silent autopilot.

•

Scoped trust

Roles, capability checks, restaurant scope and supported audit events are part of the operating model.

•

No marketplace

We don't compete with our restaurants for the customer. Cibus runs your service, not a consumer brand on top of it.

•

Tenant isolation

Restaurant tenants are separated through database row-level security and scoped application access.

What we build

One platform, five families of products

01Run
Service operations
POS, KDS, QR Order & Pay, Staff Mobile, Payments & Receipts, Admin Dashboard.
02Grow
Customer & growth
Storefront for online ordering, Reach for marketing campaigns, Stories for AI-drafted content.
03Deliver
Own delivery
Rider for dispatch, courier tasks and proof of delivery — tied to the order.
04Intelligence
AI & reporting
AI Insights for owner-reviewed briefings, analysis and recommendations.
05Partner
Sales partners
Sales Agent Portal for scoped partner-managed portfolios, onboarding and commissions.

Where we're going

The direction of the platform

•

Tighter operations

Continuing to compress hand-offs between POS, kitchen, payments and delivery.

•

Better restaurant intelligence

Deeper AI Insights and operational analysis, with the operator reviewing each recommendation.

•

Deeper customer engagement

More natural QR, Storefront and Reach flows — same operating layer.

•

Broader multi-location support

Continue developing group menus, scoped roles, cross-site reporting and partner-managed rollouts.

•

More languages, more markets

Cibus is built for a multi-language restaurant market with RTL-first care.

•

Never a marketplace

Cibus will not become a consumer food-delivery brand. Our customer is the restaurant.

Operating commitments

How Cibus approaches trust

✓

Restaurant-first, never a marketplace

We won't compete with restaurants for the diner.

✓

Website leads are not sold

Cibus does not sell website-lead information. Product-data responsibilities are defined in the applicable customer agreement and privacy notice.

✓

Owner-reviewed AI

AI features draft and recommend. Owners review and decide. Nothing autopilots.

Company details

The organisations behind Cibus

✓

United Kingdom

Cibus AI Ltd · Company 15873165 · 7 Alford Road, Stockport SK4 5AW, United Kingdom.

✓

Malaysia

NSD Multi Resources Sdn Bhd · 201601021643 (1192582-T) · 37-2, Jalan Kuchai Maju 11, Kuchai Entrepreneurs Park, 58200 Kuala Lumpur, Malaysia.

✓

Initial regional focus

The first localized commercial editions are the United Kingdom, followed by Malaysia in English, Malay and Simplified Chinese.

✓

Editorial responsibility

Abbas is the named author and substantive reviewer of the four published Cibus buyer guides. Product, legal and language review remain separate approval roles where required.

Connected