One Platform. One Data Layer. Nine Applications. Real-Time Everything.
“The technology disappears. The value stays.”
Five layers, one platform. Every ECA application reads and writes from the same data layer. No ETL, no sync jobs, no duplicate data.
The digital twin thesis: a single Farm object in the OODB is the source of truth. Every application renders its own view of the same data — no duplication, no sync.
→ When an exporter updates their farm data, every application sees the change instantly.
Eight purpose-built taxonomies encode the structure of Ethiopia’s coffee sector — regions, varieties, processing methods, certifications, and more.
SpacetimeDB is not a database with an API bolted on — it is a stateful compute engine that pushes every change to every connected client over WebSocket.
All clients receive updates instantly via persistent WebSocket connections. No polling, no webhooks, no delayed sync.
Bidding events with <100ms latency. Every participant sees every bid as it happens — fair, transparent, real-time.
OPI scores, member counts, compliance percentages — all update as data changes. No refresh button needed.
“When an exporter updates their lot availability, every buyer browsing the Atlas sees it immediately.”
Spark agents use MCP tools to read and write OODB data. The platform IS their working memory — they don’t need external databases, APIs, or data stores.
Key insight: Each agent uses MCP tools to read and write the OODB — the platform is persistent working memory for AI, not just a database for humans.
The conventional approach — Salesforce for CRM, Shopify for commerce, custom code for compliance — creates data silos, integration tax, and vendor lock-in.
| Capability | Fermia | Salesforce + Shopify + Custom |
|---|---|---|
| Single data layer | One OODB | 3+ databases + ETL pipelines |
| Real-time | WebSocket native | Polling / webhooks / batch sync |
| Dynamic schemas | OODB — no code required | Custom development per schema change |
| AI agents | MCP integrated, native access | Separate AI layer, API bridges |
| Cost (5 years) | ~$50K/year | ~$200K+/year |
| Vendor lock-in | Open source stack | Proprietary platforms |
| Offline-capable | Client-side data cache | Cloud-dependent |
| Ethiopia data sovereignty | Self-hosted option | Data in foreign jurisdictions |
Technology deployment aligned to the B³ project portfolio — each phase delivers operational modules that unlock the next.