Platform · Osage Cloud

Platform

Une seule surface, un seul plan de contrôle.

What you get out of the box

Application deploys — any container, any language; Git push, Dockerfile, or Docker Compose; one-click templates for common stacks.
Databases — SQLite via Osage Base (default), ClickHouse for analytics, Redis, MySQL, MariaDB, MongoDB where required. No production PostgreSQL by policy.
Ingress — Osage Gateway with built-in static and routing plugins. Automatic TLS, HTTP/3, edge caching, route weighting.
IAM — one sign-in at osage.id across every app you deploy.
KMS & secrets — Osage KMS as root of trust; per-org Key Encryption Keys; envelope encryption is a first-class column type in Base.
Observability — Prometheus / OpenTelemetry / Grafana stack on by default; structured logs, traces, metrics, real-user monitoring.
Backups — Litestream WAL streaming for SQLite; scheduled snapshots for object storage; documented restore runbooks.
Multi-node — scale apps across multiple nodes via Docker Swarm or hand off to Kubernetes (k3s, k8s) for larger workloads.
Notifications — deploy success/failure, alerts, capacity events via Slack, Discord, Telegram, email, or your own webhook.
CLI & API — manage everything from the terminal or your own automation; OpenAPI spec published.

Architecture — kept simple

One API binary. A single Go binary (osage-cloud) imports every backend (compute, storage, databases, AI gateway, crypto, robotics, agents) and serves them under one multi-tenant API. Runs as api.osage.cloud.
External IAM. Osage IAM (iam.osage.id) is the auth backend. Orgs and projects are Supabase-style isolations.
Console is separate. console.osage.cloud is its own Next app with its own SQLite backend; reads live state from the API and dashboards from the analytics store.
One analytics store. ClickHouse, shared across every console (customer, operator, Osage) for analytics + o11y. One pipeline, one query surface.
Everything else is SQLite. Via Osage Base, with the CEK envelope, Litestream replication. No exceptions.

Sign-in and tenancy

Every Osage Cloud customer gets one Osage IAM tenant (iam.osage.id) and one or more applications registered as osage-<app>. Users sign in once at osage.id and have SSO across every app you deploy.

Platform inquiries: [email protected].