Koo Docs
View as Markdown

Introduction

What is Koo

Host your work free, for life. Koo takes a GitHub repository, a container image, or the code on your machine, runs it on Koo's hosting layer, and keeps it running with live logs, metrics, and one-click rollback. Everything runs from standard container images, so your work stays portable.

Free, for life

Your first account includes an always-free allowance: one web service, one Postgres database, and one Redis database — each 0.5 vCPU / 1 GiB, forever, with no credit card and no trial clock. Resize a service and the free share still applies — see the free tier for how the allowance works.

The free tier is not a trial. The allowance never expires, and running inside it never requires a card.

Three ways to deploy

Pick whichever fits your project:

  • A GitHub repo — Koo builds from your repository, and can deploy on every push once you turn auto-deploy on. See Deploy from Git.
  • A container image — bring any public or private image and Koo ships it. See Deploy a container.
  • Your machine — run koo up in your project directory and the CLI uploads and deploys your code. See koo up.

You can also let an AI coding agent do the deploying for you — see Deploy with AI.

How Koo is organized

Five nouns cover everything — Projects & environments walks through the full model:

  • Account — your identity and the billing unit: a handle, a team with roles, and a plan. Your first account is your primary account and carries the free allowance.
  • Project — a named home for one piece of work. Creating a project also creates its production environment.
  • Environment — one running copy of a project (production, staging, a preview). Its canvas is where you see and change your services.
  • Service — one running part of an environment: a web service, a Postgres database, or a Redis database.
  • Deployment — an immutable, numbered version of one service. Every deploy creates one, and rollback returns to a previous one.

Show the world

Publishing is an explicit act — nothing you deploy is listed anywhere until you publish it. When you want an audience, publish an app page: a public listing for what you built, with discovery, upvotes, comments, and follows. Your account doubles as a public profile that others can follow.

Where to go next

  • Quickstart — sign in and take your first service live in about ten minutes.
  • API — drive Koo from code, CI, or agents.