Developers
Managed does notmean opaque.
QIOI handles the infrastructure work, but the platform is built to be inspectable: structured templates, observable deployments, readable logs, and data you can take with you.
What you get
The surface developers actually touch.
No control-panel archaeology. These are the capabilities exposed to every account, plus the ones rolling out next.
API access
A developer API is on the roadmap. Early access is available via contact for teams with a concrete integration need.
Custom domains
Point your own domain at any instance. DNS guidance and SSL issuance are handled by the platform.
Logs
Application and deployment logs from the dashboard, with credentials scrubbed before anything is written.
Backups
Scheduled encrypted backups with restore and on-demand snapshots. Backup behaviour is defined per template, not improvised.
Easy upgrades
Plan upgrades resize the instance through the provider adapter. Application upgrades follow tested stable or LTS channels.
Exportable data
Download backups and export application data at any time, in formats the upstream application actually uses.
Application templates
Templates are metadata, not pages.
Every application in the catalogue is a structured template: container images, minimum resources, ports, volumes, environment variables, health checks, backup policy, and update channels. The dashboard, the docs, and the deployment pipeline all render from the same definition.
Adding an application to QIOI means writing and testing a template — not building a bespoke deployment. That is what keeps the catalogue consistent and the update path predictable.
interface ApplicationTemplate {
id: string;
slug: string;
name: string;
description: string;
category: AppCategory;
containerImages: ContainerImage[];
minimumResources: ResourceRequirement;
recommendedPlans: string[]; // plan ids
ports: PortMapping[];
volumes: VolumeMount[];
environmentVariables: EnvVarSpec[];
healthCheck: HealthCheckSpec;
backupPolicy: BackupPolicy;
updateChannels: ("stable" | "lts")[];
isPublished: boolean;
}Conceptual CLI preview
What driving QIOI from a terminal could look like.
This is a design sketch, not a shipped tool. It shows the shape of the workflow the developer API and CLI are being designed around.
qioi — conceptual preview
$ qioi deploy openwebui --plan m --region ca-central → template openwebui resolved (stable channel) → plan M: 4 vCPU · 8 GB RAM · 160 GB NVMe → region ca-central · provider selected automatically → monthly estimate: $69 hosting + management proceed? [y/N] y → deployment queued · watch with: qioi status qio-8f2a41 $ qioi backup create qio-8f2a41 → snapshot scheduled · encrypted at rest $ qioi logs qio-8f2a41 --follow → streaming application logs (Ctrl-C to detach)