About

Built in the open. Shaped by operators.

We already run Caterlord — the POS behind 7,000+ restaurants across APAC. X1 is the new product line we are rebuilding from the ground up, as the industry's first AI-native, open, community-driven POS.

Why X1, why now

We already run the POS for 7,000+ restaurants. So why rebuild from zero?

Caterlord — our incumbent product — is a mature, battle-tested POS serving thousands of F&B brands across APAC since 2013. It works. It prints receipts. It closes tills.

But POS architecture from the 2010s is closed by design. Operator data sits behind a vendor, roadmaps arrive as quarterly emails, integrations require sales calls, and the idea of pointing an AI agent at your business is a three-year IT project.

X1 is our answer. A new product line, built from the ground up around three principles the old world can't retrofit: AI-native, open documentation, community feedback. Caterlord continues. X1 is where we are placing the next decade.

2013

Caterlord launches in HK

First-generation POS for F&B operators across Asia.

2018

ODO — QR code ordering

Launched ODO, our QR-code ordering product — one of the first in the HK market.

2021

7,000+ shops on Caterlord

Expanded to TW, SG, AU. Proven at scale — QSR, full service, chains.

2025

The AI shift

Operators start asking: "can my Claude agent read my sales?" The honest answer on legacy POS: no.

2026

X1 — new product line

Rebuild from zero. Cloud-native. Hosted MCP. Open docs. Public feedback.

First principles

Three principles.
Not retrofits.
The product is shaped around them.

Industry first

AI-native

X1 is the first POS designed around the assumption that every operator works with an AI copilot. We ship an MCP server so Claude, Cursor, and your custom agents can read sales, inventory, attendance, and device health — OAuth-scoped, tool-by-tool.

Docs + feedback

Open by default

OpenAPI 3.1 REST. HMAC-signed webhooks. A hosted MCP server. Product documentation and public feedback live in GitHub — fork the docs, correct them, PR them, or file feedback for the team.

Public feedback

Community-driven

Bugs, feature requests, and product feedback go through the public feedback repo. Operators can see what has been filed, add context, and talk directly to the team building it.

Built in the open

Not a marketing claim. Go check the public repos.

The public surface is intentional: X1.Doc for documentation and X1.Feedback for bugs, feature requests, and customer-facing discussion. Core product code and the MCP server remain private.

Feedback tracking, public.

Bugs, feature requests, and feedback tickets live in X1.Feedback on GitHub Issues. File one, watch the progress, and add context without a support black-hole.

github.com/caterlord/X1.Feedback · Issues

284 Open

1,912 Closed

Labels · Milestones · Sort

Open

Feature: batch-edit modifier groups from HQ menu editor

#1847·by @mei-chan · Kaffeineenhancementhq

In progress

Bug: KDS station filter resets after printer reconnect

#1823·by @james-chow · Ramen Hachibugkds

Planned

Feature request: auto-86 threshold per item, not per category

#1819·by @hotpot-wongenhancementinventory

Open

Docs: MCP scopes table is stale for v0.4

#1808·by @kerry-hkdocs

Docs, public.

Every page of our docs lives on GitHub. Fork it for your internal wiki. Fix a typo and PR it. Translate it into your language. Operators have already merged 234 PRs.

github.com/caterlord/X1.Doc

caterlord / X1.DocPublic

Official X1 documentation. Edit, fork, or file a PR — this is how the docs get better.

412 stars87 forks234 PRs merged

Recent contributions

Fix typo in MCP scopes table@jaco-tw2 days ago

Add zh-HK translation for Pricing page@riceroll-cafe1 week ago

Update Stripe Terminal setup guide@lucas-sg2 weeks ago

Browse the repos on GitHub→Read the MCP docs

2013

Caterlord Launched

7,000+

Caterlord shops live

Regions · HK / TW / SG / AU

200M+

Transactions / year

Join the build

POS used to happen to you. X1 happens with you.

Book a demo, file your first feature request, or just browse the issue tracker. That is how operators end up shaping the product.

Book a demo→Open GitHub

caterlord/X1.Doc

Public docs. Fork, edit, PR.

caterlord/X1.Feedback

Public bugs, feature requests, and customer feedback.