00Flagship case study
Trazo OS: the cultivation floor and the regulator work from one record.
The deepest system Aptixx has built: 117 of 117 tables under row-level security, 210 versioned migrations, and a 60,000-line Metrc module configured for 26 US jurisdictions. Aptixx designed and engineered Trazo OS under contract for Trazo Global Inc. It runs cultivation facilities — cannabis and produce — from the room and the batch through to the compliance report.
01By the numbers
Evidence a reviewer can re-check against the running database.
Tenant isolation, per-endpoint permissions and jurisdiction-by-jurisdiction compliance live in the schema, where they can be counted.
210
versioned database migrations
117/117
tables under row-level security, verified live
60,000
lines in the Metrc compliance module
26
US jurisdictions configured
Alongside these: 200+ application routes, nine operational roles carrying 50+ permissions, a separate Health Canada CTLS engine, and an 11-job telemetry and alarm pipeline. Every figure on this page is countable in the repository or the database it came from.
02Context
Cultivation is manufacturing with a regulator attached.
A multi-site cultivation business runs a production floor and produces regulatory evidence from the same set of facts. Those two jobs have to share one record, or they drift apart.
Facilities are split across sites, buildings and rooms. Plants move in batches through defined stages, are weighed, split, destroyed, packaged and transferred — and every one of those events is both an operational fact and a reportable one. In the United States, that report goes to Metrc under a state license. In Canada, it goes to Health Canada through CTLS. The tolerance for a mismatch between what the floor did and what the regulator was told is zero.
Trazo Global Inc. holds the product. Aptixx is the team engaged to design and engineer the platform end to end — architecture, schema, modules, compliance integrations and delivery.
03The operational problem
Compliance fails in the seams between tools.
Batches, rooms, inventory, purchasing, tasks, sensors and compliance reporting arrive as seven separate tools. The gaps between them are where the numbers stop agreeing.
- 01Batches move through propagation, veg, flower, harvest and cure, while the record of where each one sits lives on a whiteboard.
- 02Rooms and zones are run by whoever is on shift; environment readings sit in a vendor dashboard nobody reconciles against the batch.
- 03Inventory and purchasing live in a second system, so what finance counts and what the grow team weighs quietly disagree.
- 04Tasks and SOPs are assigned in a chat thread, which is not evidence when an inspector asks who did what, and when.
- 05Regulatory reporting is re-keyed by hand into the state system, from numbers that were already entered once somewhere else.
04The system
One tenant-isolated platform, from the room to the regulator.
Trazo OS holds sites, rooms, batches, inventory, purchasing, tasks, sensor telemetry and compliance reporting in a single multi-tenant system, where every table is isolated per organization and every endpoint checks a permission before it answers.
The spine of the platform is the batch. Batches sit in rooms, rooms sit in sites, and the weights, movements, splits, destructions and packages recorded against a batch are what the inventory, purchasing and task modules work from — one record of the facility rather than five exports somebody has to reconcile on a Friday.
Compliance sits at the end of that same spine. Reportable events come out of the operational record rather than being re-keyed into a regulator's portal from it — which is what reconciles when an inspector compares the two.
Tenant isolation
Multi-tenant from the schema up, not bolted on at the query layer. A live database audit recorded row-level security enabled on 117 of 117 tables.
→ 117/117 tables under row-level security, verified live
Roles and permissions
Nine operational roles carrying more than 50 distinct permissions, enforced on every endpoint rather than by hiding buttons in the interface.
→ Authorization checked server-side, on every request
Operations modules
Batch lifecycle, inventory, purchasing, task and CRM modules working against one record of the facility instead of five exports.
→ One record from propagation through to sale
Telemetry and alarms
A sensor telemetry and alarm pipeline running on 11 scheduled jobs — ingestion, alarm evaluation, aggregation and recurring task generation.
→ 11 scheduled jobs behind the alarm pipeline
US compliance
A Metrc integration module of 60,000 lines, configured for 26 US jurisdictions, with signed Metrc API agreements held in multiple states.
→ 26 US jurisdictions configured
Canadian compliance
A separate Health Canada CTLS module. Canadian reporting is its own regime, so it gets its own implementation instead of a translation layer over Metrc.
→ CTLS handled on its own terms
210 versioned database migrations sit behind that schema. Structure changes by reviewed migration, in order — never by hand against a live database.
05The standard
Control you can audit, not architecture you have to take on trust.
Multi-tenancy, per-endpoint authorization, jurisdiction-by-jurisdiction compliance, an 11-job telemetry pipeline and a schema that has survived 210 migrations. Aptixx made those architectural decisions and carries them in production.
Those are the defaults Aptixx builds to: tenant isolation you can audit against the database, authorization enforced in the server rather than the interface, and regulatory reporting generated from the operational record. If your business runs under a regulator, hold the build to that standard — see how Aptixx approaches regulated operations software.
The same problem shows up without the license. Multi-site production and manufacturing operations carry the same batch-and-evidence burden, and the marine draft-survey platform answers it with calculations and signed documents that stay defensible years after they were issued.
06Trust controls
Isolation you can audit. Permissions you can point at.
Security posture in a multi-tenant regulated platform is a set of facts you can re-check against the running database.
- 01Tenant isolation is audited against the live database rather than asserted in an architecture diagram — the audit recorded row-level security enabled on 117 of 117 tables.
- 02Authorization is enforced per endpoint. Nine roles, more than 50 permissions; a hidden menu item is not an access control.
- 03Compliance integrations are configured per jurisdiction and gated by signed Metrc API agreements, held in multiple states.
- 04Schema change is versioned. 210 database migrations, applied in order, reviewable — production structure is never edited by hand.
The jurisdiction rules, endpoints and payload contracts for 26 US jurisdictions are configured in one module, with signed Metrc API agreements held in multiple states.
07Next step
Compliance reports assembled by re-typing are the first seam to close.
If your operation carries a license, a multi-site floor and a compliance report assembled by hand from numbers entered somewhere else, the first move is a scoped look at that workflow.
Start with how Aptixx builds regulated operations software, or go straight to the paid discovery sprint, where the workflow gets mapped, the integrations get de-risked, and the build gets defined before anyone commits to it.
Regulated operations engineering →
Fixed fee, $3,500–$9,500 USD, set in writing before work starts. You keep the workflow map, the build definition and the budget band whether or not Aptixx builds it; if you proceed, the fee is credited against the build.
Next step
Bring the licensed operation and the report it files.
20 minutes on your floor, your reporting obligation, and where the two stop agreeing. Free, and you leave with a straight read on fit and the next step either way.