Cloud, cells, One3 Box and edge
One kernel that runs in the cloud, on premises and at the edge
One3 is planned to run the same kernel and Packs everywhere. Pooled cloud cells serve most tenants, while One3 Box and edge nodes are designed for sovereign, regulated and offline sites.
Same kernel, different profiles
One3 Box and edge nodes are planned to run the same kernel and Packs as the cloud. A deployment profile (cloud, box, airgap or edge) switches features and model routes on or off.
That means one product, one Action contract and one set of policies, wherever it runs. A tenant does not have to choose between AI features and keeping data on site. The trade-offs are explicit: local boxes run smaller open-weight models, and air-gapped boxes use no cloud models at all.
Deployment stages
| Stage | Where it runs | Purpose |
|---|---|---|
| S0 (months 0-5) | A 24/7 build machine with Docker Compose and local models. Every machine-dependent task has a cloud fallback. | Development, CI, staging, AI Lab, internal use |
| S1 (months 5-9) | Build machine for staging plus small cloud production in an India region | Design partners with real data |
| S2 (month 9 to Year 2) | Cloud Kubernetes, one production cell in India, disaster recovery in a second region | General availability, first tenants |
| S3 (Years 2-3) | Multi-cell (India, EU/US), silo cells for enterprise, a dedicated GPU pool | Scale and enterprise |
| S4 (Year 3 onward) | Adds One3 Box on-prem appliances and edge nodes | Sovereign and offline |
No production data on an office machine
The build machine is for development, CI, the AI Lab and batch jobs. The plan rules out hosting paying customers' production data on a single office machine. Design-partner production runs in a cloud region from S1.
Isolation tiers
| Tier | How | For whom |
|---|---|---|
| Pooled | Shared Postgres with tenant_id on every row, Row-Level Security and per-tenant keys for sensitive fields | SMBs and agency sub-accounts |
| Bridge | Dedicated schema or database on a shared cluster, dedicated vector collections | Mid-market and regulated tenants |
| Silo | A dedicated cell (database, workers, optional GPU) in the chosen region | Enterprise, BFSI, government |
| Sovereign | One3 Box on premises or air-gapped, with open-weight models | Defence, government, data-sovereign buyers |
Cells: limiting blast radius and keeping data in region
From Year 2, One3 plans a cell architecture. A cell is a full copy of the stack serving a set of tenants.
A global control plane holds the tenant directory, billing and identity federation. It routes each tenant to its cell. A problem in one cell stays in that cell, and each cell can sit in the region a tenant's data must stay in.
Planned region cells
| Cell | Purpose | Timing (gated on demand) |
|---|---|---|
| India (primary) | Home market, DPDP | W1 |
| India DR | Resilience | W2 |
| Middle East (UAE / Saudi) | Indian diaspora businesses and data residency asks | W4 candidate |
| Southeast Asia | SMB and agency markets | W4-W5 candidate |
| EU | GDPR and AI Act compliance, enterprise | W5 candidate |
| US | Largest SaaS market, state privacy laws | W5 candidate |
| Sovereign / customer-hosted | One3 Box | W5 |
One3 Box tiers
| Tier | Target buyer | Workloads | Honest constraints |
|---|---|---|---|
| Box S (SMB / branch) | Shops, clinics, small factories, schools | Offline POS, inventory and desk; local small models; embeddings; speech recognition; cloud sync | Limited model quality and concurrency; frontier features need cloud, by policy |
| Box E (enterprise rack) | Mid-large enterprises, hospitals, BFSI branches | Full One3 stack; mid-size open models; per-tenant adapters | Capital cost; needs on-site IT or partner-managed operations |
| Box G (air-gapped / government) | Government and regulated sectors | Full stack with open-weight models only; offline update bundles | No cloud models; slower updates; certification needs vary by buyer |
| Edge Node | Warehouses, stores, vehicles, field sites | Offline apps, local sync, vision inference, IoT gateway | Small models only; remote management essential |
Updates and management you control
Box hardware specs in the plan are illustrative planning targets, to be validated with benchmarks and partners. The software model is set.
Three update channels
Stable (quarterly), LTS (annual, with security patches) and airgap (signed offline bundles delivered through an approved process).
Signed releases
Signed images, SBOMs and customer verification tooling, with reproducible builds as a goal.
Reviewed model bundles
Curated open-weight models, each with a licence review and eval report per release.
Opt-in remote management
Connected boxes can report health, updates, backup status, GPU use and security posture.
Break-glass support
Support access is customer-approved, time-boxed and recorded.
Partner hardware
One3 does not manufacture hardware. Certified configurations, warranty and installation are planned through OEM and implementation partners.
How offline-first sync is designed to work
The event log is the unit of sync between edge, Box and cloud.
- 1
Work continues locally
Events append to the local log while the site is offline.
- 2
Replicate on reconnect
Local events replicate when the connection returns. Actions carry idempotency keys, so replays are safe.
- 3
Apply conflict rules
Low-risk fields use last-writer-wins, collaborative text uses CRDTs, and stock and money follow domain rules.
- 4
No silent merges for money
Financial conflicts go to an exceptions queue for a person to resolve.
- 5
Re-check policy
R3 and R4 Actions queued offline are re-validated against policy on sync, for example if prices changed while offline.
The Edge, IoT & Compute app by wave
| Module | What it does | Earliest wave |
|---|---|---|
| Maps & Location | Territories, beats, routes and visit verification | W4 |
| Edge Sync | Offline scopes, queue, conflict rules and site edge nodes | W4 |
| Frontline Worker App | Checklists and tasks with photo evidence and Indian-language voice | W4 |
| IoT Hub | Sensor rules that create work orders and tasks through Actions | W5 |
| Vision AI | Camera-agnostic edge inference with privacy masks | W5 |
| Kiosk & Digital Signage | Playlists with content expiry and POS-synced boards | W5 |
| One3 Box Manager | Releases, health checks and licences for appliances | W5 |
| One3 Compute | Quota-bound GPU jobs with costs posted to AI FinOps | W5 |
| Spatial Work Instructions (AR) | Step-by-step procedures and remote assist | W6 |
| Robotics Bridge | Robot missions from One3 events via vendor fleet managers | W6 |
Guardrails for the physical world
- The Edge app is outside the Year-1 boundary. No feature of it is built in Year 1 or W3.
- Box updates, diagnostics exports and support sessions need customer approval. Licence expiry degrades to read-only and never locks data.
- Vision face identification is off by default. Detections and geofence exits are signals for a human, never automated adverse decisions about people.
- Robot missions go through vendor fleet managers, whose safety systems stay in charge.
- Location tracking runs only on shift, with notice. Regulatory points are pointers only. Verify with counsel.
Deployment plan in numbers
- deployment stages, S0 to S4
- 5
- isolation tiers
- 4
- One3 Box and edge tiers
- 4
- update channels
- 3
- Edge, IoT & Compute modules
- 10
Deployment questions
Can One3 run inside my own data centre?
That is the plan for One3 Box. Box E is a rack for enterprises and Box G is air-gapped for government and regulated buyers. Sovereign deployment is planned for W5.
Where will my data be hosted at first?
The first production cell is planned in India from W1, with disaster recovery in a second India region in W2. Other regions are candidates gated on demand.
Does an air-gapped box get AI features?
Yes, with limits. Air-gapped boxes run open-weight models only, with no cloud models and a slower update cadence.
What happens to offline sales or stock changes?
They are stored as local events and replayed safely on reconnect. Financial conflicts are never merged silently. They go to an exceptions queue.
Does One3 sell hardware?
No. One3 plans certified configurations from hardware partners, with partner warranty and installation and One3 software support.
Discuss sovereign or offline needs
If your data must stay on site or your sites go offline, talk to our team about the deployment plan.