Projects

Your own project in seconds. In Kaja, projects are where your apps run. You spin them up when you need them and tear them down—or pause them—when you're done. No more waiting on DevOps. No more paying for idle resources. For app features in depth, see Apps.

What is a project?

A project is your own isolated space on a cluster. Think of it like a folder for a project or a branch: everything you deploy lives inside that project. Each project is separate from the others, so you can have a "dev" project, a "staging" project, or a personal project per developer—all on the same cluster, all manageable from one dashboard.

What you get:

• Spin up in seconds — Create a project from the dashboard. Kaja sets it up on the cluster you chose. Start deploying right away.
• Pause when you're done — Stop paying for idle resources. Pause the whole project (everything in it stops) or pause individual apps. Resume whenever you need to work again. Savings happen automatically.
• Duplicate or save as a template — Copy a live project into a new one, or capture it as a reusable template you can spawn environments from later. See Templates & duplication.

You create projects per cluster. Pick the cluster, give the project a name, and you're set.

Creating a project

1. In Kaja, open your organization and select the cluster where you want the project.
2. Go to Projects and click Create project.
3. Enter a name (e.g. dev, staging, alice-preview) and, if you like, a display name.
4. Optionally start paused if you don't want anything running until you're ready.
5. Submit. Kaja creates the project and you can start adding apps.

That's it. No tickets, no manual setup — one place to spin up and manage.

Pause and resume

Pause stops everything in that project so you're not paying for idle resources. Use the pause action for the project (or for a single app). Resume brings it back when you need it. This is Kaja's approach: you stay in control, and you stop paying when you're not using the project.

You can pause the whole project or just one app. Your choice.

Templates and duplication

Duplicate copies a live project into a new one — optionally onto a different server — bringing its apps, config, services, and domains with it. Save as template captures the project's shape as a reusable template stored at the organization level, so you can spawn fresh environments from it later.

See Templates & duplication for what carries over and what to check before you confirm.

What runs inside

Inside a project you deploy apps from your own container images — create them, pause them, update them, and view logs and metrics from one place. Your apps can also use managed services (databases, caches, tools) that Kaja runs for you. For a full breakdown (scale, variables, health checks, auto-scale, helpers, and more), see Apps.

Next steps

• Apps — App features, config, and observability in depth.
• Managed services — Add databases, caches, and tools from the catalog.
• Logs & metrics — See what's happening in your apps.
• Quick start — End-to-end from sign-up to first project and app.