JustShipIt

You describe it · agents build it

The last tool you need to build a SaaS.

Describe what you want your product to do, in your own words. Agents write it, test it and put it online for you — and they keep going while you sleep. What they build is live on its own address, and it is yours.

you describe, they build they work while you sleep live on its own address the code stays yours 14 days free, then €49/month

workspace — checkout-api up 6d 04h
running https://checkout-api.mira.justshipit.cloud

An agent is asked, in one sentence, to add invoices to the billing page. It reads the app, changes four files, runs the tests and saves the work. The new version builds, its address and certificate are ready, and the app is live at checkout-api.mira.justshipit.cloud — one minute fifty-eight in total, with the laptop closed.

Agents

Your agents don't stop when you close the laptop.

An agent works on your app around the clock, on our machines rather than yours, and everything it needs is already set up for it: your code, permission to change it, and claude, codex and opencode already installed. Close the tab, shut the lid, get on a plane — it keeps working.

  • It remembers where it was. Stop it and start it again next week: what it had learned about your app and the work it had half-finished are still there.
  • It sees what the app sees. Same cluster, same database, same logs — not a mock of them.
  • Its commits ship themselves. An agent push is a push: build, preview, deploy, and a diff you can read before it goes anywhere near production.
code-checkout-api.mira.justshipit.cloud running
Uptime
6d 04h 12m
Agents installed
claude · codex · opencode
Repository
mira/checkout-api · cloned, push key
Home volume
kept across stop / start
Last agent commit
9f2c4ab · 4 minutes ago

How it works

Ask for it, and the next thing you see is it live.

Three steps, and only the first one is yours. The first version is online about two minutes after the agent finishes — and so is every change after it.

  1. STEP 01

    Say what you want

    Describe the app, or the next change to it, in a sentence. The agent starts from a working project rather than an empty folder, so there is nothing to set up first. Already have code somewhere? Bring it in from GitHub or GitLab and it picks up from there.

  2. STEP 02

    The agents build it

    They write the code, run the tests and save the work — every change signed, dated and readable, because each one is a commit in your own git. Nothing is decided in a dashboard you cannot audit later.

  3. STEP 03

    It goes live on its own

    No release to run and no certificate to buy: the new version is built, checked and published for you — by Argo CD, Traefik and cert-manager, if you care which. You get app.yourname.justshipit.cloud immediately, and your own domain whenever you point it at us.

Hosting

Your code lives in a git you own, in Europe.

Not a mirror of someone else's. The forge runs on this platform, on hardware in Germany, and it holds both your application and the file that describes how it runs. The console is a nice way to edit that file — that's all it is.

  • Edit it from either side. Change it in the console, commit it yourself, or let an agent do it — same file, same result.
  • Every change is attributable. Who changed what, when, and the diff — because it's a commit.
  • Leaving is a clone. If you go, you leave with a working Helm chart and a Dockerfile, not an export ticket.
tenants/mira/apps/checkout-api/values.yaml main
image:
  repository: git.justshipit.cloud/mira/checkout-api
  tag: "main-9f2c4ab"   # written by the build

replicaCount: 2
resources:
  requests: { cpu: 100m, memory: 128Mi }

ingress:
  hosts:
    - host: checkout-api.mira.justshipit.cloud
    - host: api.mira.example

addons:
  postgres:
    enabled: true
    instances: 2
  valkey:
    enabled: true
    maxmemory: 96mb

Batteries included

Stop rebuilding the same wheel.

Eleven runtime templates on hardened base images, and one chart that already knows how to do the boring parts. Most of what follows is a toggle in the console — and every change it makes is a commit you can read.

Templates

Go · Node · Python · Rust · Ruby · Elixir · PHP · Java · Next.js · static · your own Dockerfile

Base images

distroless and alpine runtimes, non-root, read-only rootfs, matching build images with the toolchain already in them

The chart

ingress · TLS · health probes · autoscaling · resources · secrets · cron · add-ons

Preview environments

Open a pull request, get app-pr-12.yourname.justshipit.cloud on its own namespace. Close it and the environment is pruned. Lock previews to an IP range when they shouldn't be public.

Logs as they happen

Runtime logs stream into the browser live — not a 30-second refresh. Build logs sit next to them, one click from the failing job.

Rollback in one click

Every deploy is a commit, so every rollback is one too. Pick a past deploy, read the diff, and the platform commits the revert for you.

Bring what you already have

Import a repository from GitHub or GitLab and we add the Dockerfile and build workflow it's missing. Point its push webhook at us and it deploys on every commit, wherever it lives.

Managed data

PostgreSQL on CloudNativePG and a Valkey cache are add-ons on a toggle. Backed up on a schedule with Velero, restore included.

Secrets that stay out of git

Environment variables and secrets live in OpenBao and are projected into the pod. Change one and the deployment rolls itself — no redeploy to remember.

Domains and TLS

Point a record at us and the certificate is issued and renewed without you. Wildcard hostnames for every app and every preview come with the account.

Usage and cost, per app

CPU, memory, response time and a running monthly cost for each app — in the same console, not a separate billing portal you forget exists.

Built on
  • Talos Linux
  • Cilium
  • Argo CD
  • Traefik
  • cert-manager
  • CloudNativePG
  • OpenBao
  • Forgejo
  • VictoriaMetrics

Isolation

One cluster to run. One of your own to use.

The heavy machinery — GitOps, secrets, identity, metrics — runs once on a hub cluster. Your account gets its own virtual cluster with its own API server, its own quota and its own namespaces, so a noisy neighbour stays a neighbour.

The hub holds no tenant credentials. Every account is fenced by a separate Argo CD project, a separate secret policy and a separate identity group — three locks, not one.

hub cluster argo · openbao · sso · metrics mira vcluster · 6 apps theo vcluster · 2 apps jun vcluster · 4 apps you vcluster · day one
Region
Germany · Hetzner
Node OS
Talos — no SSH
First deploy
~2 minutes
Backups
Scheduled, restorable

Pricing

Four plans. Fixed prices, no meter running.

Fourteen days free to start — a card, no charge, cancel inside the fortnight and you pay nothing. After that the plan price is the whole bill: nothing is measured, nothing is added on top. The agents, CPU, memory and storage on a plan are ceilings shared across that plan's apps. Above Starter the app count stops being the thing you buy: apps are unlimited, and the CPU and memory are the size of the plan.

Starter

€49/ month + VAT

For a first app or two, and the side project after it.

  • Up to 3 apps
  • 2 agents building at once
  • 2 CPUs and 3 GB across them
  • 20 GB of storage

Scale

€249/ month + VAT

For a product with services, environments and room to grow.

  • Unlimited apps
  • 6 agents building at once
  • 14 CPUs and 22 GB across them
  • 200 GB of storage

Dedicated

Machines reserved for you alone rather than shared — your own node pools, sized to what you run. Agreed case by case.

Talk to us →

A fourth app on Starter means moving up a plan — plans change from the console, whenever you like. Start free — 14 days →

Your first app is a push away.

Pick a runtime and push, and watch the URL come up. If it isn't live in a couple of minutes, we'd want to hear about it.