About

Why cidbee exists.

Every business ends up duct-taping spreadsheets, five tools and a half-written wiki into something that half-works. We think the operating system beneath it should be buildable by the team using it — not bought feature-by-feature.

The origin

cidbee started as an ERP-in-the-small: small/mid businesses picking between a spreadsheet ceiling and a rigid enterprise suite. The answer we kept circling was generalized. Not "a CRM with better fields" — a platform where the team defines its own tables, formulas and permissions, and automation is a first-class citizen you can read, fork and run safely.

What we believe

• Tenant-scoped, always. No query runs outside a resolved tenant scope; there is no privileged backdoor into tenant data.
• User code is a feature, not a leak. Sandboxed V8 functions extend the product honestly — with zero ambient authority, brokered under the Permission Engine.
• One expression language. Formulas, conditions and filters speak the same grammar, so knowledge transfers everywhere.
• No spare parts. The whole platform is one coherent stack, deployable as an independent unit — shared or BYODB, cloud-hosted or on-prem-capable.
• Open formats. Own your data and your animations. Exports are plain JSONL/CSV; branding and even the Lottie files on this site are ours, auditable.

The team

A small crew of platform engineers and product people who have shipped identity, sandboxing and data modelling at scale. We run cidbee on cidbee — dogfooding the permission engine, the automations and the sandbox every day. Open roles are listed on /careers.