Put your app online.Keep it running.
Connect a repository. Eigon works out what your app needs, sets up the servers and the database, and gives you a live address. No Dockerfile, no Terraform, no cloud console.
Then it stays on call. When something breaks, Eigon tells you what broke and why in plain English, proposes the change, and lets you roll back in one click.
Run it on Eigon, or in your own AWS account if you would rather own the infrastructure. Spend cap either way.
No account, nothing deployed. Eigon reads your repo and tells you what it would take to run it.Monthly spend cap, set once
Failures named, not logged
Your AWS or ours
Production · eigon-api
Last deploy · 2 min ago · Healthy
Deployment timeline
- ✓ Trigger · maya@eigon.dev
- ✓ Clone & build · main@c14a92b
- ✓ Release to cluster
- ✓ Health check · 200 /healthz
- ✓ Completed · 38s
Runtime profile
0.5 vCPU · 1 GB RAM · 2 replicas
Start: npm run start
Live logs
10:02:12 · deployment queued (production)
10:02:14 · cloning repo github.com/org/app@main
10:02:22 · build succeeded in 8.2s
10:02:27 · rolling out to cluster (2 replicas)
10:02:34 · health check passed (200 /healthz)
10:02:35 · deployment completed · v42
Keep building on
First question
“Will this even work with my code?”
Paste a repository URL. Eigon reads it the way it would before a real deploy. What language and framework it is, what it needs at runtime, which services it would provision, what it would cost per month. Then it hands you the answer.
No account. Nothing deployed. Nothing charged. If the answer is “this needs work first”, that is a useful thing to know for free.
Scan my repo free- ·Language, framework and package manager, detected from the repo
- ·The services it would need: database, cache, worker, queue
- ·An estimated monthly bill before anything is created
- ·Anything that would stop a deploy, named up front
Second question
“What happens when it breaks at 2am?”
This is the part a platform team normally does. On most platforms a failed deploy hands you a build log and a stack trace and wishes you luck.
The cause, in one line
Eigon reads the container's own crash output, not the build log, and says what failed. “Cannot find module dist/server.js”, not “exit status 1”.
Plain English logs
Crash. Restart. Error rate. Written for someone who has never opened CloudWatch.
A proposed change
Eigon suggests the fix, applies it, redeploys, and records whether that worked. It will not reuse a fix until it has worked three times.
One-click rollback
Back to the last good version. 24 hour window per deploy, no console required.
And when that is not enough, a person answers.
Support is a human reading your actual deployment, not a chatbot and not a link to the docs. Every paid plan includes it, Pro is prioritised, and on the $99 setup we do the first deploy with you on a call. If the problem turns out to be ours, fixing it is our job and we will tell you that rather than patch your code around it. A workaround that happens to work would only hide that we are broken.
You build the app. Eigon gets it running.
Connect your repository. Eigon reads your code, works out what it needs, provisions it, and deploys. Keep building in Cursor, Claude Code, Lovable, Bolt, or a plain editor, on an app no AI has touched.
First app? Start here.
You do not need to learn cloud infrastructure to put something online. Eigon decides what your app needs and sets it up, and the parts you would normally have to understand first, like a container image, a network or a database, are decisions it makes and explains, not homework.
No Dockerfile, Terraform or YAML required.
If something is wrong with the code, you get told which line and why.
Already shipping? Skip the setup you keep redoing.
Less time configuring. More time shipping. →
Run in Your Cloud or Ours
Bring Your Own Cloud
Run entirely in your own cloud.
- · Eigon connects to your AWS with a secure read role
- · Server and database run in your account
- · You own everything. Eject any time
- · No vendor lock in
Ideal for startups and teams that want control.
Eigon Managed Cloud
Don't want to manage your own cloud yet?
- · We host your services
- · Automatic scaling and environments
- · Built-in observability
- · Seamless upgrade to your own cloud later
Ideal for fast-moving teams.
How it works
- 1Connect your repository
Push from Replit, Bolt, v0, Lovable, Cursor, or any repo. Import and select a branch.
ReplitBoltv0Lovable - 2Configure environments
Add environment variables, resources, and domains.
Variables·Resources·Domains - 3Deploy
We build, release, run health checks, and give you a live URL.
Auto-buildHealth checks - 4Manage & scale
Monitor, redeploy, and roll back anytime.
MonitorRollback
Example: production rollout
Repository
github.com/startup/app
Environments
Domains
app.yourstartup.com
Third question
“What will it cost me?”
You set a dollar ceiling once. Eigon throttles before the bill goes past it, and tells you on the way up rather than at the end of the month. Bandwidth alerts sit on the same ladder.
Because the infrastructure is in your own AWS account, you can also see the bill yourself. Eigon's subscription and your cloud spend are two separate numbers, and we never quote them as one.
Eigon Managed is one bill instead of two. Same cap, same alerts.
What the cap actually does
- ·You name a monthly ceiling in dollars.
- ·Eigon warns you as spend climbs toward it.
- ·At the ceiling it throttles rather than letting the bill run.
- ·A traffic spike or a scraper cannot turn into a four-figure invoice.
Everything else you get
A URL you can hit
Dev gives you a direct address. Staging and production add a load balancer and your own domain.
Managed database and cache
Postgres and Redis provisioned with the app, not as a separate afternoon.
Prod, staging and dev
Separate environments with their own variables, sized differently.
PR preview environments
Every pull request gets its own URL to test against.
Blue/green releases
New version up before the old one goes down.
Reads code no human wrote
Lovable, Bolt, v0, Cursor. No Dockerfile required. Eigon writes one.
Your cloud or ours
Run in your own AWS account or on Eigon. Move between them.
AI copilot for infra
Ask it to add a database, scale a service, or change a domain.
CLI, MCP and GitHub Actions
Deploy from a terminal, your CI, or an AI agent with a scoped token.
Typed failures, not log dumps
Stable codes an agent can branch on: USER_CODE or PLATFORM_CONFIG, with a one-line hint.
WAF on production
A default firewall, and egress alerts on the same ladder as the spend cap.
Drift detection
If something changes your infrastructure behind Eigon's back, you hear about it.
Deploying is the easy part
Getting an app onto the internet is a solved problem. What usually is not: keeping it off the public internet, handing it to one colleague, and finding out that a dependency you did not choose has broken you.
Put a password on it. Write no code.
Flip one switch and your app asks for a password before it serves anything. The check happens at the CDN edge, before a request reaches your code, so there is nothing to add to your app and nothing to maintain.
For the internal dashboard that should never have been public, and the client preview you do not want indexed.
Share it like a document
Send someone a link and they can open your app. No Eigon account, nothing to sign up for. Each link belongs to one person, so you can turn theirs off without changing the password for everyone else.
Links can expire. Revoking one takes effect on your next deploy, and Eigon says so rather than pretending otherwise.
Safe to run code you did not write
Eigon reads your source for things shaped like credentials before it runs it, and explains what it found instead of just refusing. You can also stop an app reaching anything except the places you name, so pasted code cannot post your data somewhere you have never heard of.
Nothing is ever sent anywhere to be tested, and Eigon never stores the value it found.
Told when an update would break you
Eigon watches the registries for the packages you actually depend on and tells you whether moving to the new version breaks a caller — not just that a newer version exists. When it can, it opens the pull request.
Only the packages you chose yourself. The hundreds pulled in underneath them are watched and counted, not put in front of you.
Why teams choose Eigon
Shipping fast shouldn't mean rebuilding later.
Eigon gives you the simplicity of modern deploy tools with a real production setup. Ship today, scale when users arrive, see what is happening in plain English. No platform team required.
Who is it for?
Anyone who does not want to pay for a devops team to put an app online.
Solo builders on a first project. Agencies running a dozen client apps where devops cost scales with the client count. Small teams whose fifth deploy still takes an afternoon of setup.
An app generated by Lovable or Cursor and an app typed by hand deploy the same way. Eigon reads what is in the repository, not what wrote it.
From prototype to scale
Start small. Eigon picks a server and database size for today and shows you the monthly cost before it creates anything. Resize when you need to, from the dashboard.
Trust & safety
- Secure networking
- Encrypted configuration
- Audit history
- Controlled access
FAQ
Ready to ship your vibe coded app to real users?
Connect GitHub, pick an environment, and your app is live on a real server in a few clicks.
Simple plans. Same price everywhere.
You own your AWS. We deploy it. You control it.
Starter
$29/month
One app, live, on infrastructure you own.
- 1 app
- Your own domain
- Prod + staging
- No sleep
- Free for your first 30 days
- Email support
Pro
$99/month
For apps with users on them.
- 3 apps
- All environments, plus PR previews
- Auto-fix proposals and rollback
- Eigon Copilot
- 5 seats
- Priority support
Scale
$199/month
For a studio or a team running several apps.
- 10 apps
- 15 seats
- Everything in Pro
- Spending caps per app
- Drift detection and Terraform export
- Compliance report for SOC 2, GDPR and HIPAA controls
Enterprise
Custom
More apps, more seats, or terms of your own.
- Apps and seats negotiated
- Agencies running client work under one account
- SSO and custom IAM (roadmap, scoped per contract)
- Dedicated onboarding and support channel
- Compliance templates and audit support
Plan price only. Cloud usage is billed by AWS in your own account, or added separately on Eigon Managed. We never quote the two as one number.
Cloud usage billed separately if you run on Eigon. On your own AWS, you pay AWS direct.