Oneop is one system for the work a business actually does — built by the people who have to use it.
Oneop is an AI customer platform: chatbot, live chat and governed AI agents on top of a CRM, a help desk, a double-entry general ledger and a warehouse system that all share one database. It is founder-led, and every claim on this page is one you can check inside the product.
Why Oneop was built
Oneop was built because the software a small company runs on is a pile of tools that disagree with each other.
The pattern is familiar to anyone who has run one. A CRM holds the customer. A separate help desk holds the conversation. Invoicing lives somewhere else again, stock lives in a spreadsheet, and the books are reconstructed monthly by someone reading exports. Each tool is good. The seams between them are where the numbers stop matching, and the seams are what a small team spends its week on.
The alternative usually offered is a suite — separate products behind one login, kept in step by syncs that run on a schedule. That moves the seam; it does not remove it.
Oneop takes the other route: one PostgreSQL schema, one tenant boundary, and modules that read the same rows instead of copies of them. That is the entire thesis, and the page that argues it in detail is Why Oneop.
What Oneop is, in plain terms
Oneop is a multi-tenant SaaS platform for small and mid-sized businesses that want their customer conversations, sales pipeline, invoicing, stock and books in one place.
- Category
- AI customer platform with an integrated CRM, help desk, finance and inventory system.
- Company
- Oneop, an independent, founder-led software company.
- Product surface
- A web application at
app.oneop.io, an embeddable web chat widget, and an official WordPress plugin. - Customer channels
- Web chat and email, both landing in one shared inbox.
- AI provider
- Google Gemini, reached through one metered router.
- Interface languages
- Eight, fully translated — Arabic, German, English, Spanish, French, Turkish, Urdu and Simplified Chinese, with genuine right-to-left support for Arabic and Urdu.
- Availability
- A free plan with two seats, no credit card, available now.
How the product is actually built
Oneop's engineering rules are conservative on purpose, because the product holds other people's money and stock. Four of those rules are visible in the codebase rather than in a values statement.
Additive migrations, never destructive rewrites
Schema evolution runs through 225 hand-written, idempotent SQL migrations. Re-applying one is a no-op. New tables and columns are added rather than existing ones renamed or dropped, which is the unglamorous reason an upgrade does not take a customer's data with it.
Off means invisible, not locked
Finance, statutory tax, project management, sales sequences, email-to-ticket, e-signature and two-factor are all opt-in. While one is off, its routes return 404 and its schedulers do not run — it is not a locked door with a marketing banner on it. Anything touching money, stock or someone else's mailbox stays closed until a human turns it on.
Fail-closed defaults
A misconfiguration should stop work, not do it wrongly. Webhook signature verification refuses an unverified payload rather than trusting it. A shipping label will not be bought if no origin address is configured. A foreign-currency document will not be created if no exchange rate is on file for its date. An AI agent set to full autonomy still cannot post a bill or issue a purchase order while the finance-actions flag is off.
Isolation enforced at the data layer
275 of the platform's 329 tables carry a tenant ID, enforced on every query at the data layer rather than filtered in the interface. There are three separate login principals — the tenant app, the internal operator console and the client portal — each with its own cookie and its own signing secret, and production refuses to start if those secrets are not all distinct.
That posture is backed by tests rather than intent: 165 automated test files, including a guard test that breaks the build if any AI agent file calls a model provider directly or omits the tenant ID from a metered call.
Every claim on this site is checkable
The numbers on these pages — 329 tables, 225 migrations, 165 test files, nineteen integrations, eight translated languages — are counted from the codebase, not rounded up for a headline.
- Security is described as mechanisms. Which controls exist, how they behave, and what happens when one fails, on Security.
- What shipped is dated. The changelog records what landed and when.
- What is coming is written in the future tense. The roadmap separates shipped, opt-in and next, and never dresses one up as another.
- Integrations are named vendors, not a logo wall. Each one on Integrations says exactly what it syncs and in which direction.
How to reach Oneop
The fastest way to evaluate Oneop is to open a free workspace; the fastest way to reach a human is email.
Existing customers reach support at support@oneop.io. Everything else — pricing questions, turning on an opt-in module, migration questions — goes through Contact, or book thirty minutes on a demo.
Get started
Start free, and read Why Oneop while it sets up.
Open a free workspace with two seats and see the product this page describes, rather than take our word for it.
Sign-up opens when the app launches. We will email you once — no marketing list.