kuiper Docs

Get started

Overview and quickstart

Kuiper deploys Glove Foundry and Station agents. Install the CLI, sign in, deploy an agent and watch it come up.

On this page

What Kuiper does#

Kuiper is a deployment platform for agents, the way Vercel is for Next.js apps. You give it code. It builds the code, runs it, gives it a public address and keeps it running.

  • It knows your framework. Glove Foundry apps and Station daemons deploy without a Dockerfile or a config file. Kuiper detects them and picks the build, the start command and the port. Any other Node app deploys too, once you give it a start command and a port.
  • It keeps state. Foundry and Station units get a persistent disk at /data. Logs survive crashes and redeploys. Managed Postgres, Redis and object storage run inside your project.
  • It shows you the agent. The dashboard reads runs, signals, conversations and events straight from your running agents. There is nothing to wire up.
  • It stays out of the way. Variables, secrets, domains and rollbacks are one command or one click each.

The pieces#

You will see these words everywhere in the dashboard and the CLI.

TermWhat it is
OrganisationThe team that owns everything. Everyone in it sees every project.
ProjectA group of units that belong together. Secrets, databases, buckets and domains belong to a project. It has a name and a slug, the short handle you pass to -p.
UnitOne agent or service you deploy. Each unit has its own address, logs and deployments. A unit is an agent (the default), a station daemon or a service.
BuildTurns source, a Git push or an uploaded folder, into an image.
DeploymentOne image running as a unit. Deployments are numbered #1, #2 and so on. One is live at a time.
VariableA setting a unit reads from its environment. Its value is a template, so it can point at a secret, a database or another unit.
SecretA value Kuiper stores sealed and never shows again.

Quickstart#

You need a Kuiper account. If you do not have one yet, request early access. You also need a folder with a Glove Foundry app, a Station daemon or a Node app.

  1. Install the CLI.

    curl -fsSL https://app.kuiper.sh/install.sh | sh

    Check it with kuiper --version. More in Install and sign in.

  2. Sign in.

    kuiper login

    Your browser opens the dashboard and shows a short code. The terminal shows the same code. Approve it in the browser and the CLI receives its own API token.

  3. Create a project and a unit.

    Terminal
    kuiper projects create my-agent
    kuiper use my-agent
    kuiper units create web

    kuiper use sets the default project, so you can leave out -p from now on. The unit is called web, which is also the default for -u. Deploying a Station daemon? Create the unit with --kind station.

  4. Deploy your folder.

    Terminal
    cd path/to/your-agent
    kuiper deploy --source . -u web --wait

    The CLI uploads the folder, streams the build log, then prints each step of the rollout until the deployment is live.

    Output
    uploading 38 files (96 KiB) as your-agent@3f9c2a1
    …
    live ✓
  5. See it live.

    Terminal
    kuiper status -u web
    kuiper logs -u web -f

    status prints the unit's address and its live deployment. logs -f follows the output. Open the address in your browser, or find the unit in the dashboard.

The project overview in the dashboard: one card per unit, with a log preview, its address, status and live deployment.
The project overview. Every unit gets a card with its address and live deployment.

Prefer the dashboard? Open New project, pick a repository or drop a folder, and press Deploy. Deploying covers all three ways in.

Where to go next#