Product architecture

How ODYXOS is built — and how the parts connect.

A core spine of records that never disagree, business and specialist modules on top, intelligence that reads the same data, and shared platform services underneath.

Information flow

What flows where.

FromToWhat travelsStatus
CRM leadDirectory · ProjectContact, client and property, deduplicatedLive
Scan3D plan · Studio designEstimateQuantities by room and zone; design linesLive
EstimateProposalA frozen version for the clientLive
Proposal approvalContract baselineApproved total, created once, immutableLive
VariationsContract ledger · EconomicsApproved changes as new versionsLive
Purchasing · TeamEconomicsCommitted and actual costBeta
EconomicsInvoicingThe cap: current contract valueLive
InvoicingAccounting programmeIssued and received invoices, once, with conflict detectionBeta
ODYXOS GoPlanning · Team · FinanceClock-ins, site notes, receiptsLive
ProjectClient portalProgress, photos, documents, contractLive
Security & data

Separation and permissions built in.

  • Each company’s data is resolved on the server and kept separate from every other company.
  • Eleven roles — from owner to site manager, designer, finance, purchasing and external accountant.
  • Cost, margin and forecast fields are removed on the server for roles without permission.
  • AI use is a permission, with daily limits per person and per company.
  • Secure links for proposals and contracts refuse tampered tokens.

Being completed before general availability: production sign-in with individual accounts, a durable database with file storage, and scheduled background jobs. See the roadmap

Technology

Web application on Cloudflare’s global network, a mobile web app installable on iPhone and Android, a WebGPU 3D engine running on your own device, and a multi-provider AI engine behind usage limits.

Early access

See ODYXOS on your own kind of project.

A 45-minute walkthrough with the team that builds it — from first visit to final invoice, on a real renovation example.