Internal Development Platform.

Establishes who a person or service is. Platform consoles, APIs and Git access can share an identity instead of maintaining separate accounts.

• OpenID Connect provider with single sign-on and social sign-in through Telegram, GitHub, Google and, where configured, Apple.
• Short-lived ES256-signed access tokens with refresh sessions. Services verify tokens through JWKS discovery rather than sharing a secret.
• API keys for command-line tools and Git, plus generated TypeScript and Swift clients.

Decides what an authenticated identity may do. Keeping permissions out of the identity provider lets every service define its own scopes without changing how people sign in.

• Users, groups and role assignments scoped to a service and a resource.
• A shared backend client, so product services check permissions the same way.
• Permission mutations and their audit events commit in the same transaction.

Stores each project's configuration as immutable revisions and delivers values to running workloads without passing them through CI.

• Every change creates a new revision; a release pins the exact revision it was deployed with.
• Scoped delivery: a host receives only the values for the workloads it runs, through one-time grants.
• A command-line client for pulling and pushing local environment files.

A custom self-service control plane on top of PostgreSQL. Projects get databases and database users through one API instead of manual administration.

• Database and user provisioning with per-database access grants.
• Separate permissions to use the service, create databases and administer it, granted directly or through groups.
• The same API behind a web console, a CLI and a generated client.

S3-compatible object and bucket storage based on MinIO, with a custom web interface and single sign-on through auth.rc.

• Standard S3 API, so applications use ordinary S3 clients and tooling.
• MinIO is pinned to a release that keeps OpenID Connect sign-in for the console.
• Stored data and its configuration are managed separately from application releases.

Collects a bounded set of product events and turns them into fixed reports. The collector and protected dashboard are live; client enrollment is progressing through a controlled pilot.

• One event catalog generates typed TypeScript, Swift and Rust event definitions.
• Ingestion keys are scoped to a project, environment, platform and component, and cannot read data.
• Browser and native clients queue events locally and retry with stable event IDs for deduplication.
• Reports sit behind auth.rc sign-in and groups.rc permissions.

Hosts the monorepo's single canonical repository. Developers push here; GitHub receives an ordered replica for Actions and integrations and is never an alternate place to write.

• Authenticated browsing and Git access, limited to members of the developer group.
• Durable, ordered mirroring: every accepted push is queued and replayed with a lease, so a diverged replica stops the queue instead of being overwritten.
• A documented recovery procedure that preserves both histories if the replica ever diverges.

A provider-neutral view of workflows, runs, jobs, logs and artifacts. It is separate from how pipelines are defined, which is covered under shared tooling.

• GitHub Actions is the implemented provider; other providers are not yet supported.
• Live run updates from webhooks, workflow graphs and failure annotations.
• Provider credentials are stored per connection rather than as global settings.

Each project declares its deployment targets. The control plane keeps release history, schedules work and coordinates host runners that perform the deployment.

• Promotes immutable releases of Docker services, static sites, CLI channels and systemd artifacts.
• Health-checked promotion and rollback to a retained release. Migration barriers gate traffic changes; application rollback does not reverse database changes.
• Runtime secrets come from pinned secrets.rc revisions, not from CI.
• Fenced claims, idempotent requests and consistent lock ordering coordinate recovery. Uncertain migration outcomes require operator reconciliation.

General-purpose KVM virtual machines on bare-metal hosts. The control plane owns access, machine metadata and action history; a Go host agent translates requests into libvirt and cloud-init operations.

• Machine images, cloud-init, SSH keys and private networks.
• Lifecycle controls and per-machine metrics.
• Persisted guest network mappings are validated and restored idempotently when the host agent restarts.

The task tracker that the monorepo's own work runs on, used from a browser and from the command line.

• Spaces, tasks, comments, saved views and boards.
• Progress pipelines: a task is complete when it reaches the last stage, not when a box is ticked.
• A command-line client for scripts and coding agents.