stack qioi tree
Four layers. One dependency direction.
The ecosystem is a stack, read bottom-up: physical compute, managed operations, trusted knowledge, vertical applications. Each layer is built to be useful without the ones above it.
dependency tree
spaceone ── physical compute + data centres
· servers
· gpu
· storage
· networking
· power
· colocation
· canadian data sovereignty
└─ qioi ── managed deployment + operations ◄ you are here
· provisioning
· orchestration
· domains
· ssl
· auth
· monitoring
· backups
· updates
· rollbacks
· billing
└─ deepfryr ── trusted knowledge + rag
· citations
· provenance
· version tracking
· confidence levels
· conflict detection
· entity resolution
· human-review workflows
└─ vecondo + future verticals ── evidence-first condo intelligence
· building history
· repair history
· permits
· dated events
· confidence scoring
a stack, not a trap
independently valuable
each layer is useful on its own — deepfryr does not require vecondo, qioi does not require spaceone.
external providers today
qioi runs on attached external providers right now. spaceone capacity is standby, not a prerequisite.
no forced migration
you are never required to move providers, regions, or layers to keep your service running.
exportable at every layer
backups, data, and configurations leave with you. portability is a design requirement, not a favour.