← Documentation

Managed services

Services are the databases, caches, and tooling your apps depend on. You add one from a catalog, Kaja provisions it inside your own project, and connection details are wired into your apps for you.

Everything runs on your servers. Kaja provisions and manages it; it never leaves your infrastructure, and there is no per-service fee.

Adding a service

  1. Open a project and go to Services.
  2. Pick a service from the catalog and choose its options—size, replicas, persistence, and so on. The options differ per service.
  3. Create it. Kaja installs it into the project's namespace and tracks its health.

Connection binding

When a service exposes a connection, Kaja generates the credentials and stores them in a secret inside the same project. Instead of copying a password into your app's environment by hand, you bind the app to the service and the values arrive as environment variables.

This matters more than it sounds: the credential is generated once, never displayed in plain text, and rotating it doesn't mean hunting through every app's config.

The catalog

Available now:

  • Observability — Metrics and logs together, in one click. It installs a metrics store and a log store with lightweight, project-scoped collectors.

In the catalog, landing soon:

  • PostgreSQL — Production-ready Postgres with HA, backups, and automatic failover.
  • Redis — In-memory store for caching, sessions, and queues.
  • Grafana — Dashboards, auto-wired to whichever metrics and logs backends you have installed.

Services marked coming soon are visible in the catalog so you can see what's arriving, but can't be provisioned yet.

Services change what the platform does

This is the part that makes services more than a package manager. Installing a service can change how Kaja itself behaves.

Install Observability, and your apps' logs and metrics start coming from that service rather than from raw Kubernetes—longer retention, real queries, proper history. You didn't configure a data source or point anything at anything; the platform noticed what you installed and rewired itself.

The same pattern applies as the catalog grows: what you install determines what the console can show you.

Next steps

  • Apps — Bind a service to an app.
  • Logs & metrics — What Observability turns on.
  • Projects — Services are scoped to a project.