my-appengineer

Build your app with AI. Own the infrastructure it runs on.

Describe the app. Agents plan it, build it and deploy it into your own cluster — with your kubeconfig, your git repo, your Postgres and your domain. €19 a month, flat. No credits.

free · no card · your cluster from the first sign-up
kubeconfig download git clone your repo Postgres in your namespace your domain, auto-HTTPS
From the community

Live apps, not screenshots.

View all in Explore →

Shipped by people who described an idea, approved the plan, and let the agents build it into their own cluster. Publishing is one click — or keep an app private.

Sound familiar?

Built it in a weekend. Then hit the wall.

Three of the most-upvoted posts in the rooms where people build with AI today.

Replit charged me $1,982 in 24 days on a pre-launch app with 1 user — me

r/replit

If you are building without 'Ejecting' you don't own your startup

r/lovable

The deployment problem is the biggest unsolved pain point for no-code/AI builders in 2026

r/nocode

Every AI builder rents you the place your app lives — and meters every prompt. Every self-hosting tool hands you a server and leaves you to write the app. Nobody did both. So we did: the agents that build your app, and the cluster that runs it, in one product. You hold the keys to the second half from the first sign-up.

Both halves

The builder, and the place it runs.

Other tools stop at the first half and rent you the second. Here the second half is yours — a real Kubernetes cluster under your account, from day one.

half one · the agents

AI agents build it

Describe the app in plain language. The agents propose a plan, you approve it, and only then is code written — so you know what you're getting before you get it.

  • Plan first. Every build starts with a plan you approve — not a surprise.
  • Real code, real URL. Each build ships with HTTPS to yourapp.you.my-app.engineer or your own domain.
  • Iterate by chatting. A feature, a fix, a redesign — ask, and the live app changes.
  • Your own AI key on Pro. OpenRouter or Ollama — the message allowance disappears. No token markup.
half two · your cluster

Your cluster runs it

Your account comes with its own Kubernetes control plane over your own isolated space. Download a kubeconfig and kubectl works. Standard Kubernetes — not a proprietary box.

  • Bring your own nodes. Put Tailscale on a machine at home, click Add as node, paste one line. It's in.
  • Or rent a machine. A Hetzner server joins your cluster as a worker in under a minute; you pay only while it runs.
  • Already running things on a VPS? Pair it and get a migration plan for what's on it.
$ kubectl --kubeconfig ~/Downloads/my-app.kubeconfig get nodes NAME STATUS ROLES AGE VERSION you-cp Ready control 2m v1.31 desk-pc Ready worker 40s v1.31 # your machine, via Tailscale
Who it's for

Made for the people who already built something — and got stuck at the part that isn't building.

r/lovable · r/vibecoding · r/nocode

Founders who vibe-coded

You built it on Lovable, Bolt, v0 or Replit. The export sits in a folder. Bring the idea here; the agents rebuild and deploy it into a cluster you hold the keys to.

How a rebuild works →
r/replit · r/SaaS

Leaving a credit meter

Effort-based billing turned a hobby into a $1,982 invoice. Here the number is €19 and it does not move when you prompt more.

See the two prices →
r/selfhosted · r/homelab

Self-hosters & homelabbers

You already trust Coolify or Dokploy. This is the same ownership — kubeconfig, your nodes, your Postgres — with the agents that write the app included.

The keys you get →
IT · DevOps · small teams

Small teams & IT

A namespace per user, quotas, Kubernetes Dashboard read-only or full admin, EU hosting or your hardware. Nothing exotic to audit — it's Kubernetes.

Governance notes →
The keys

Own it. Not "export it later" — from the first build.

Ownership you can check yourself, tonight, instead of a promise on a pricing page. Each key comes with the command that proves it.

kubeconfig

Your cluster

Standard Kubernetes with your own control plane. The Cluster tab hands you a kubeconfig; the Kubernetes Dashboard opens as full admin if you like.

kubectl get pods -n you
git

Your code

Every app has its own git repository with full history, under your username. Clone it with your own credentials, any time, to anywhere.

git clone gitlab.my-app.engineer/tenants/you/freshcuts
postgres

Your data

Your app's database runs inside your cluster in plain PostgreSQL — reach it with the tools you already know. One click downloads everything we hold about your account.

kubectl exec -n you freshcuts-db-0 -- psql
vault

Your keys

Your AI provider, your Stripe account, your domains — stored in a per-tenant vault and injected into your apps. Never copied into the workspace, never readable by another tenant.

kubectl get externalsecrets -n you
nodes

Your nodes

The machine under your desk, the NAS on the shelf, a rented server — join them to your cluster and the apps run on hardware you chose and can unplug.

kubectl get nodes
domain

Your name on it

Point your DNS at us, click once; the certificate is issued and renewed for you. The app answers on your domain, not ours.

curl -sI https://yourdomain.com | head -1
Compare

A self-hosted Lovable alternative — with the builder included.

Every AI builder on the left rents you the second half. Every self-hosting tool skips the first. This is the only row with two checks.

ToolAI builds the appRuns on infrastructure you ownHow you pay for AI
LovableYesNo — Lovable CloudCredits
Bolt.newYesNo — their cloudTokens
ReplitYesNo — Replit's infrastructureUsage-based, effort-billed
v0YesNo — VercelCredits
DyadYes, locallyNothing runs — you deploy it yourselfFree, your own key
Coolify / DokployNo builderYes — your VPSFree, open source
my-app.engineerYesYes — your own Kubernetes cluster, your nodesFlat plan · your own key on Pro

As published on each tool's pricing page and docs, September 2026. Corrections welcome — hello@my-app.engineer

The last 30%

Payments, analytics, brand, social — one click into your cluster.

The part every AI builder leaves you to figure out. Each tool installs into your own cluster, signs you in automatically, and is yours alone.

Kubernetes Dashboardfree

Workloads, YAML, logs and exec — in your own cluster. Read-only or full admin, you choose at connect.

Ghost Browsertool

A real, logged-in browser with an HTTP API your agents can drive. Research, sign-ups, the tasks that need a human-shaped browser.

Till · Moneytool

Stripe accounts, products, payments and bookkeeping — over an API your agent can use to add checkout to any app.

Pulse · Markettool

Every app's visits, sign-ups and activations, counted first-party in your cluster. No third-party script.

Crest · Brandtool

Brand creation — voice, look, story. Crest knows who the brand is, so every app and post agrees.

Herald · Socialtool

The social-media manager — composes, schedules and posts in the brand's name, from your cluster.

Plus the open-source stack you'd otherwise install by hand — Grafana, Prometheus, Loki, cert-manager, MinIO, Velero, Kyverno, Falco and more — rolled out into your cluster with one click. Paid tools carry one flat monthly price each: you pay for the tool, never per prompt.

Pricing

A number you can plan around.

No credit meter on your prompts. A monthly allowance you can see on the built-in AI — or bring your own key and there is no allowance at all.

Free
€0

No card. Your own cluster included.

  • 1 app, on your own Kubernetes control plane
  • 10 AI messages a month on the built-in AI
  • 0.5 vCPU · 1 GB · 10 GB — sleeps when idle
  • Live URL with HTTPS, Explore, the tools catalogue
Start free →
Pro
€19/ month, flat

The whole second half: dedicated cluster, your hardware, your key.

  • 10 apps
  • A dedicated cluster — your own k3s, not a shared control plane
  • Join your own machines as nodes over Tailscale
  • Bring your own AI key (OpenRouter / Ollama) — unlimited messages
  • 1,000 messages a month on the built-in AI if you'd rather not
Start on Free, upgrade inside →

Need more metal? Rent a Hetzner machine from the Cluster tab — prepaid credit, billed only while it runs, and it joins your cluster as a worker in under a minute. Paid tools are a flat monthly price each, cancel any time; a lapsed tool keeps its data. Most people we read are paying $25–100 a month for a builder plus $20–59 for hosting and a database, and still don't hold the keys.

Fair questions

The things people ask before they sign up.

I don't know Kubernetes. Is this for me?

Yes — that is the point. Your cluster is created with your account and the agents deploy into it; you never write YAML or touch a node unless you want to. Kubernetes is there when you reach for it (a kubeconfig download, the Dashboard, a cluster buddy that explains what it sees) and invisible when you don't.

Isn't this just another platform to be locked into?

It's designed so the answer is checkable rather than promised. Your cluster is standard Kubernetes you hold a kubeconfig for. Your code sits in a git repository under your name that you clone with your own credentials. Your database runs in your namespace in plain PostgreSQL. Your nodes are machines you can unplug. If you leave, you take it — nothing needs our staff to release.

What does it cost next to Lovable + Vercel + Supabase?

Pro is €19/month, flat, for ten apps and the dedicated cluster. Add your own AI key and there is no message cap and no markup on tokens. Compute is yours: a machine at home costs you electricity; a rented Hetzner worker is billed only while it runs. There is no credit meter anywhere on the platform — a surprise bill for "effort" cannot happen here.

Is an AI-built app really production-ready?

You approve a plan before a line is written, every build ships with HTTPS on real Kubernetes, and you can instrument it with Pulse and take payments through Till from day one. The apps in Explore are live, not screenshots. We are honest about the rest: the agents get better every week, and you can always open the code.

Where does my app run — and can it run on my own hardware?

By default in the EU, in your own isolated space on our cluster. On Pro you get a dedicated cluster and can join your own machines over Tailscale — the box under your desk, your NAS, your own VPS — so the app runs on hardware you own, reachable through your domain.

Can I bring an app I built on Lovable, Bolt or v0?

Bring the idea and, if you have it, the exported code as reference. The agents rebuild it here — plan first, then code — so it deploys cleanly into your cluster. There is no automatic importer; the rebuild is the honest path, and it usually takes an afternoon.

How it works

Four steps. One live app — in your cluster.

01

Sign up free

Your private space and your own Kubernetes control plane come up with your account. No credit card.

02

Describe it

Plain language. The agents answer with a plan — what they will build, in which steps.

A booking site for my barber shop with online payments
03

Approve, then watch it deploy

Only after you approve is code written. It ships with HTTPS to your URL, in your cluster, in about a minute.

04

Own it & grow it

Add your domain, connect Till or Pulse, join your own machine, clone the repo. Ask for changes whenever you like.

Stop renting the place your app lives.

Describe it, approve the plan, and it's running in a cluster that's yours — in about a minute. Free to start, no card.

← Back to home
my-appengineer

Welcome back

Sign in to your workspace.

or continue with email
Don't have an account? Create one
← Back to home
my-appengineer

Create your account

Free to start — no card required.

or sign up with email
Already have an account? Sign in

Reset your password

We'll email you a reset link

Choose a new password

Enter it twice to confirm

Describe a business. Get the whole company running.

Your app is built and hosted on a Kubernetes cluster you own. Then the parts a company actually needs — a browser with your logins, a brand, a market, money, outreach — connect to one agent that works them while you sleep.

Loading what your space can hold…

01 / BUILD

You describe it, agents write it

A blueprint you can edit first, then real code — frontend, backend, database, deploy config. Not a template.

manager → builder agents
02 / HOST

It lands in a cluster you own

Your own space, your own domain, your own nodes — rented by the month or your hardware at home. Not a slot on ours.

k3s · your namespace · your keys
03 / RUN

An agent runs it as a business

The Master hunts demand, builds and prices the offer, then works it toward a sale through the organs below.

master + organs + a real browser
The body

One agent. Real hands. Organs that each do one job well.

Every part is a tool you can open yourself, with its own database in your space and your platform login. The Master is the only one that reads them all — connect what you need and leave the rest dark. Tap any of them to see what running it takes.

Herald speaks in public, LeadFlow speaks in private. The desk answers where somebody asked. The moment they say “DM me” or leave an address, the conversation moves to the private half — and never before.
Till counts the money, Pulse counts the market. One is what was actually paid; the other is who arrived, signed up and came back. A product is not working on one without the other.
Honest arithmetic

Pick the parts. See what it takes to run them.

Every organ is a real container with a real reservation — this is the same arithmetic your cluster does when it schedules them. Nothing here is throttled or oversold.

0 vCPU reserved
0 GB memory reserved
The hands, at work

What a browser with your logins can do that an API cannot.

No scraping key, no per-lookup fee, no data broker. It opens the page the way you would, reads what is actually there, and stops at the line you set.

google.com/maps · autobedrijf Rotterdam

Walk a map and notice what is missing

Opens every business, reads the category, the hours, the rating and how many it is over — then the reviews, newest and angriest, and whether the owner ever replied.

10 garages · 3 with no website
“Gebeld, niemand neemt op” — nobody answered that review
their own site · /over-ons

Break a company into its people

Their team page, then their LinkedIn: who decides, who runs the day, who feels the problem — each with the one way in that is actually open.

owner · manager · the desk
an address only when they published one
reddit.com/r/… · the growth desk

Answer where they asked

A reply drafted in your voice, in the room where the question was, at two a day per room — the pace a moderator still calls a member. You approve every one.

drafted → you approve → posted
public first, private only when invited
github.com · funded issues

Earn the runway before the product sells

Finds bounties with money already attached, judges whether the fix would actually be merged, and tracks it through PR → merged → paid.

picked → PR → merged → paid
only merged work pays
Running right now

Built here, hosted here, still up.

Loading…