Every product. One engine underneath.
Every Oadbox product inherits the same foundation. That is why a hospital system and a fleet platform can both ship with statutory billing, offline mobile and real audit trails — and why each new product takes a fraction of the time the first did.
- 12
- products in market
- 8
- industries served
- 100%
- built in-house
- Days
- to a live tenant
What every product gets for free
These are not roadmap items. They are the starting position for anything we build.
Multi-tenant from day one
Per-organisation data isolation, custom branding and independent configuration — not a shared table with a tenant column bolted on.
Granular access control
Permission keys down to the field, role hierarchies from branch agent to head office, and access that survives an audit.
Indian compliance, built in
GST, e-way bills, TDS and TCS, PF, ESI, PT, RERA and ABDM handled inside the product — not as an export you fix in Excel.
Mobile that works offline
Field apps for drivers, collection agents and parents that queue what they capture and sync the moment signal returns.
Audit trails everywhere
Field-level change tracking across every module, so who changed what — and when — is always answerable.
Reporting that ships with it
Dozens of reports and live MIS in every product, so nobody waits on a consultant to answer a Monday-morning question.
An AI layer with a job
Revenue-leak detection, drop-off alerts, utilisation insight and customer-facing assistants — applied where they change a decision.
Operated, not just delivered
AES-256 encryption, AWS infrastructure, monitoring and releases run by the same team that built the product.
How it is put together
Vertical logic sits on top. Everything below it is shared, and the boundary between the two is the reason we can move quickly without the products drifting apart.
Apps
- Admin console
- Customer & partner portals
- Field mobile apps
- Public status pages
Product modules
- Admissions · Wards · Bookings
- Trips · Batches · Collections
- Inventory · POS · Projects
- Payroll · Fees · Claims
Shared services
- Auth & RBAC
- Tax & statutory engine
- Documents & numbering
- Notifications
- Reporting & MIS
- Audit log
- AI insights
Data
- Schema-per-tenant Postgres
- Object storage
- Point-in-time backups
Infrastructure
- AWS
- AES-256 at rest
- Monitoring & alerting
- Continuous releases
What that buys you
Your data is yours alone
Every organisation gets its own schema. There is no query in the system that can accidentally cross a tenant boundary, because the boundary is structural rather than a filter someone remembered to add.
Compliance moves when the law does
Tax rates, statutory slabs and return formats live in the shared engine. When a rule changes, it changes once and every product inherits it — not one patch per product.
Nothing happens without a record
Field-level change tracking, immutable audit logs and document numbering that cannot silently skip. Built for the day an auditor asks.
Each new product is cheaper than the last
Because tenancy, permissions, billing, reporting and mobile sync are already solved, a new vertical starts at its actual domain problem. That is how the portfolio keeps growing without the products drifting apart.
Want the architecture walkthrough? We'll show you the real thing.
Tenancy model, permission matrix, compliance engine and release process — on a call, with the actual system open.