my-appengineer Docs

my-app.engineer documentation

You describe an app. AI agents build it. It goes live on a Kubernetes cluster that belongs to you — with a kubeconfig you can download, nodes you can add, and tools you can install. These pages explain how each part works and what it does not do.

Last updated 2026-09-05

The two halves

Most AI app builders stop at the first half: a chat that produces an app, hosted on their cloud. my-app.engineer adds the second half. Every account gets its own isolated space on Kubernetes with a kubeconfig (a dedicated cluster on Pro), and the app the agents build is deployed there — not on a platform you rent by the credit.

Getting startedFrom sign-up to a live URL in one chat. What the agents ask, what you approve, where the app lands. Your clusterWhat you actually own: the namespace, the kubeconfig, the dedicated cluster on Pro, the git repos. NodesAdd a Raspberry Pi or laptop over Tailscale, or rent a Hetzner machine that joins automatically. Cluster toolsKubernetes Dashboard, Grafana, Prometheus, MinIO, Velero, Kyverno and more — one click, in your cluster. Bring an existing appMove what runs on a VPS today, or bring a whole k3s cluster. Custom domains with automatic HTTPS. Plans and billingFree and Pro at €19 a month, flat. What the numbers mean and what costs extra. For teamsWhere data lives, the DPA, sub-processors, export and erasure. CompareLovable, Bolt, Replit, v0, Dyad, Coolify — honestly, column by column.

In three steps

  1. Describe the app. Type what you want in the prompt box. The manager agent turns it into a plan you can edit before anything is built.
  2. Approve the plan. Builder agents write the code, wire a database when the app needs one, and deploy to your namespace.
  3. Open it — it's yours. The app is live at <app>.<your-username>.my-app.engineer. Download the kubeconfig and kubectl get pods shows it running.

Something missing from these pages? Email hello@my-app.engineer — a person reads it.

Getting started →