The one sentence
Not a dev tool. Not a hosting platform.
An orchestration operating system for the AI-native, polyglot, edge-distributed world. Where the unit of work isn't a human typing a command — it's an intent, human or agent, routed to the right compute automatically.
"The local in localenv doesn't mean your laptop. It means your environment feels local — regardless of where the compute actually lives."
The market gap
Everyone the last wave ignored.
Vercel owns JavaScript. Heroku is dead. Nobody has rebuilt that magic for the engineers who build the infrastructure layer of the world.
Ignored by Vercel
Go engineers
gRPC, microservices, high-perf APIs
Ignored by everyone
C++ engineers
worst DX of any language community
Underserved
MLOps / AI
SSH + rsync + prayer in 2026
No solution exists
IoT fleet
Balena tried, DX is terrible
Growing fast
Agent runtime
nobody hosts agents well yet
Your pain point
Polyglot devs
multiple projects, multiple clouds
The mental model
The hotel.
You check in. You unpack. You feel comfortable. Your preferences follow you room to room, hotel to hotel, laptop to laptop. The hotel doesn't change when you switch locations.
# New laptop. One command.
npx localenv # checks in
localenv login # loyalty card
localenv sync pull # room preferences restored
# All projects. All services. All credentials.
# Everything back. Exactly as you left it.
git solved code portability
docker solved environment portability
localenv solves orchestration portability
The recipe format
Docker-compose compatible. Always.
Don't fight what works. Amplify what's broken. The existing docker-compose.yml is untouched. The .localenv.yml sidecar is optional, additive, and the sharing unit of the platform.
# your-project/.localenv.yml
name: my-rails-app
recipe: rails-postgres-redis
deploy:
targets:
- provider: oracle
account: personal-always-free
- provider: aws
account: work-account
tunnel:
enabled: true
ai:
diagnose: true
The spec is open source. The platform is proprietary. Exactly what Docker did with the compose spec.
The architecture
Right tool. Right layer.
localenv UI
React Flow canvas — zoom from world view to single service
React
localenv daemon
Unix socket, process management, log streaming, vault
Node.js
localenv CLI
npx localenv — talks to daemon, not processes directly
Node.js
localenv agent
Tiny binary on remote nodes — receive, execute, stream back
Go
device firmware layer
Garmin, embedded — vendor territory, localenv sits above
C / C++
The business model
Free tier as acquisition. Not charity.
The free tier trend is getting worse. Oracle and AWS free tiers are the outliers. localenv orchestrates what users already have — and becomes the natural upgrade path when they outgrow it.
Stage 1 — Hook
Free tier orchestrator
Maximize Oracle Always Free, AWS 12-month, Supabase 2-project limit. Users bring credentials, localenv brings intelligence.
Stage 2 — Convert
The deploy button
One click from local to live. That moment is the demo. That moment creates word of mouth.
Stage 3 — Retain
Managed hosting
Free tier expires. Traffic grows. localenv hosting is already there, already trusted. Migration cost is zero.
Stage 4 — Scale
IoT fleet + enterprise
Million device deployments. Agent-driven canary rollouts. $50k/year conversations, not $20/month.
The AI layer
Ambient awareness. Not a chatbot.
AI that increases your awareness by being aware all the time for you. Not something you open. Something running underneath everything, surfacing only when it matters.
Layer 1
Environment
what's running, where, at what health
Layer 2
Project
git history, PR status, deploy frequency
Layer 3
Resource
free tier limits, cost routing, compute
Layer 4
Fleet
IoT health, firmware versions, geography
Layer 5
Intent
not what you asked — why you asked it
"localenv isn't reactive. It's ambient. Traditional monitoring fires alerts. localenv surfaces what matters before you know to ask."
Current state
v1.1.0 shipped.
The CLI is live. One command starts your entire stack. iTerm2 split view opens automatically. Port conflicts resolved silently. Stack detection works across Node, PHP, Ruby, Python, Go, and Rust.
localenv init
localenv start
localenv info
iTerm2 split view
port conflict resolution
$PORT convention
stack detection
npm published
daemon — v0.2
vault — v0.2
deploy — v0.3