One-click deploy for almost any application — no manual rewiring.
LEco reads your repo, converts config, orchestrates Compose & Traefik, and ships on *.lh.
LEco DevOps is a free, MIT-licensed local cloud edge: point it at an app repo, and it does the heavy lifting — detect existing Docker Compose, Wrangler, and env layout · generate LEco manifests · merge Traefik routes · deploy.
Vision and mission
Every team deserves a truthful local cloud
We see a future where any developer, anywhere, runs software the way production does — real hostnames, trusted TLS, shared AI and automation — without months of bespoke wiring or vendor lock-in. LEco DevOps Open Project exists so the distance from “I cloned the repo” to “it works like staging” is measured in minutes, shaped by an open community that owns the roadmap and the code.
Deploy first. Configure never — unless you want to.
Our mission is to orchestrate the full path: read what you already built, convert it into LEco manifests, wire Traefik and Compose, and ship — one click when possible, full control when you need it. We build Platform, isolated dev stacks, and a control panel that feel like one product — free under MIT, governed by contributors, stewarded for the long run so open source stays the default way teams learn, ship, and collaborate.
What makes LEco different
Our USP: deploy first, configure later.
You should not have to rewrite every app for a new platform. LEco reads what you already have, converts it into LEco manifests and hosting slots, orchestrates the stack, and deploys — often in one click from the dashboard orleco-devops onboard.
| Step | What LEco does |
|---|---|
| Read | Scans docker-compose.yml, wrangler.toml, .env, Dockerfiles, and project layout from your Git tree |
| Convert | Builds leco.app.yaml + leco.yaml, materializes hosting/app-available/{slug}/, symlinks config without touching upstream |
| Orchestrate | Wires Compose projects, lh-network, Traefik host rules, optional Cloudflare-local bindings |
| Deploy | compose up, registry entry, route merge — reachable at https://{your-app}.lh with no hand-edited port maps |
Works for Docker Compose apps, React/Vue + API splits, Workers + Wrangler, and preset CMS/framework stacks — the same operator experience whether the source is your monorepo or a third-party checkout.
Platform
Platform is a unique LEco capability — not just settings. Run local or cloud VM deployments, curated service bundles, and isolated dev stacks from one dashboard tab (mirrored by leco-devops platform and leco-devops dev-stack on the CLI).
| Capability | What it does for you |
|---|---|
| Platform settings | config/leco-platform.yaml — deployment mode, base_domain, TLS (mkcert / ACME / static / Cloudflare), which ecosystem services are enabled |
| Ecosystem bundles | Start or stop groups of stack services (Traefik, Postgres, AI, Cloudflare-local, …) without memorizing script order |
| Dev stack builder | One-click WordPress, Magento, Laravel, LAMP/MEAN, or custom component picks — each stack is its own Compose project and network |
| Stack lifecycle | Start, Stop, Repair, Reinstall, Destroy with live logs — fix routing in place or wipe and regenerate from template |
| Cloud VM path | Selective install on a Linux VM with real domains and external LLM providers — same Platform model as your laptop |
| Bind hosted apps | Point platform.devStackId at a stack so a LEco-hosted app shares DB/redis endpoints without port conflicts |
Presets and versions live in ecosystem-stack/config/dev-stack-presets.yaml and component-catalog.yaml. Generated stacks land under platform/dev-stacks/{id}/ with Traefik routes in hosting/traefik/20-dev-stacks.yml.
Platform tab guide Dev stack isolation Cloud VM deployment
Features
Edge & networking
| Capability | What it does for you |
|---|---|
| Traefik reverse proxy | One entry on ports 80/443; route by hostname instead of :8080, :3000, … |
*.lh local DNS |
Stable URLs like https://n8n.lh and https://dashboard.lh that match how teams talk about services |
| mkcert TLS | Trusted HTTPS in the browser without fighting self-signed warnings |
| Network repair | repair-network and dashboard heals re-attach lh-network when containers drift |
Operations dashboard
| Capability | What it does for you |
|---|---|
| LEco DevOps UI | Single pane for stack status, metrics, logs, in-app docs, and service control |
| Control tab | Start, stop, restart, and repair ecosystem services without memorizing shell scripts |
| Hosted apps | Register third-party repos, Detect → Generate YAML → Register → Deploy in the UI, probe URLs, manage lifecycle |
| One-click onboarding | leco-devops onboard / init –onboard — deploy, registry, and Traefik merge in one flow |
| Built-in help | Operator and developer manuals served from the same UI you run the stack with |
Application toolchain
| Capability | What it does for you |
|---|---|
leco-devops CLI |
detect, init, onboard, scaffold, platform, and dev-stack commands — same brain as the dashboard |
| Hosted app slots | Keep upstream repos clean; overrides and symlinks live in hosting/app-available/{slug}/ |
| Isolated dev stacks | Per-team or per-CMS Compose projects (platform/dev-stacks/) with their own DB/network |
| Manifest binding | Attach a hosted app to a dev stack via platform.devStackId for shared infra without port clashes |
| Split API + UI routes | Traefik rules for React/Vue frontends and /api backends (same pattern as production edge configs) |
AI & automation
| Capability | What it does for you |
|---|---|
| Ollama | Pull and run local models; manage from the dashboard |
| Open WebUI | Chat UI at https://ai.lh wired to your local models |
| AirLLM | Ollama-compatible API for very large models on modest VRAM (layer streaming) |
| n8n | Workflow automation on https://n8n.lh beside the rest of the stack |
| AI-assisted onboarding | Dashboard flows to help scaffold and configure apps with provider abstraction |
Cloud-shaped development (optional)
| Capability | What it does for you |
|---|---|
| Cloudflare-local | R2-, KV-, D1-, and Workers-style adapters on *.lh without hitting production Cloudflare |
| Cloud VM profiles | Install selective services on a Linux VM with real domains, TLS (mkcert / ACME / static), and external LLM APIs |
| Update catalog | Track ecosystem, stack, and upstream image/release updates from the dashboard |
Use cases
Onboard an existing app in one click
Point LEco at a repo that already has Compose or Wrangler. It reads the layout, writes manifests, registers the app, merges Traefik, and deploys — you skip hand-copying ports, env files, and route YAML.
Ideal for: teams onboarding legacy or vendor apps, consultants standing up client demos fast.
Spin up a full stack from Platform
Use the dev stack builder for Magento, WordPress, Laravel, or infra-only bundles. Start gives you URLs and credentials; Repair fixes routing without wiping data.
Ideal for: e-commerce, CMS, and framework specialists who need a clean stack per customer or branch.
Develop like production — locally
Use real hostnames and HTTPS while you code. Frontend, API, and workers each get Traefik routes; no more “works on localhost:3000 only.”
Ideal for: full-stack and platform engineers validating routing before deploy.
Many apps, one machine
Materialize multiple LEco-hosted apps from separate Git repos. Each slot has its own manifest, compose merge, and Traefik fragment — without one mega-compose file.
Ideal for: agencies, consultants, and polyglot teams juggling client projects.
AI product development offline
Run Ollama, Open WebUI, and AirLLM on the same lh-network as your app. Prototype RAG, agents, and automation (n8n) without cloud API keys for every iteration.
Ideal for: AI engineers, hackathons, air-gapped or cost-sensitive experimentation.
Cloudflare Workers & bindings — locally
Start cloudflare-local to exercise R2, KV, D1, and Workers-style endpoints on *.lh. Provision bindings from leco-devops before CI deploys.
Ideal for: edge developers using Wrangler who want fast feedback loops.
Preproduction on a cloud VM
Use Platform profiles and cloud-install.sh on a VM with your domain, TLS mode, and optional external LLM providers — closer to staging than laptop-only compose.
Ideal for: small teams without Kubernetes, demos, and partner sandboxes.
How it fits together
| Layer | Role |
|---|---|
DNS (*.lh) |
Resolve friendly hostnames to 127.0.0.1 |
| Traefik | TLS termination and HTTP routing |
| ecosystem-stack | Start order, service scripts, repair, updates |
| LEco DevOps | Dashboard + APIs + docs + onboarding |
| Platform | Cloud/local settings, bundles, isolated dev stacks |
leco-devops |
CLI — detect, onboard, platform, dev-stack |
Deep dive: Architecture · LECo user manual · Platform tab
What you get
| Application | LEco DevOps — web UI + leco-devops CLI |
| License | MIT — commercial use, fork, contribute |
| Official repository | github.com/leco-devops/local-ecosystem |
| Governance | Community-owned; Open source |
| Contact | leco@techtonic.systems |
Start in minutes
Prerequisites: Docker, *.lh DNS, mkcert (setup guide).
git clone https://github.com/leco-devops/local-ecosystem.git
cd local-ecosystem
./ecosystem-stack/install-foundation.sh
./ecosystem-stack/ecosystem-stack.sh start
Open http://localhost.lh or http://dashboard.lh for the LEco DevOps dashboard.
Full first-time setup CLI reference View on GitHub
Frequently asked questions
Answers for operators, contributors, and AI assistants summarizing LEco DevOps Open Project. Structured data is published for search and LLM discovery.
What is LEco DevOps Open Project?
LEco DevOps Open Project is a free, MIT-licensed local cloud platform on Docker. It provides Traefik edge routing on *.lh hostnames, a LEco DevOps control panel, the leco-devops CLI, optional Cloudflare-local adapters, and isolated dev stacks — so teams run apps with production-shaped URLs without hand-wiring ports.
What is LEco DevOps one-click deploy?
LEco reads your existing docker-compose.yml, wrangler.toml, .env, and project layout, converts them into leco.app.yaml and leco.yaml manifests, orchestrates Compose and Traefik, and deploys — often via leco-devops onboard or the dashboard Detect → Generate YAML → Register → Deploy flow. You do not rewrite the upstream app for the platform.
What is the Platform tab?
Platform is a first-class LEco capability for local or cloud VM settings, ecosystem service bundles (Traefik, Postgres, AI, Cloudflare-local), and the dev stack builder — one-click WordPress, Magento, Laravel, LAMP/MEAN, or custom components. Each stack is an isolated Compose project with Start, Stop, Repair, Reinstall, and Destroy lifecycle actions.
What is the difference between a hosted app and a dev stack?
A hosted app is a third-party repository registered in config/leco-registry.yaml and materialized under hosting/app-available/{slug}/ with its own LEco manifests and Traefik routes. A dev stack is an isolated infrastructure bundle under platform/dev-stacks/{id}/ with its own databases and networks. You can bind a hosted app to a dev stack via platform.devStackId.
What does *.lh mean?
*.lh is the local DNS zone LEco uses (for example https://dashboard.lh, https://n8n.lh, https://ai.lh). Names resolve to 127.0.0.1 via dnsmasq or equivalent so developers use real hostnames and mkcert TLS instead of memorizing localhost ports.
Is LEco DevOps open source?
Yes. The project is community-driven open source under the MIT License. The official repository is https://github.com/leco-devops/local-ecosystem. Techtonic Systems Media And Research LLC provides operational stewardship; contributors own the codebase collectively.
How do I get started?
Clone https://github.com/leco-devops/local-ecosystem, run ./ecosystem-stack/install-foundation.sh, then ./ecosystem-stack/ecosystem-stack.sh start. Prerequisites are Docker, *.lh DNS, and mkcert. Open http://dashboard.lh for the control panel. See docs/SETUP.md for the full guide.
Does LEco support cloud VM deployment?
Yes. Use config/leco-platform.yaml with deployment_mode cloud, cloud-install.sh or install profiles, custom base_domain, TLS modes (mkcert, ACME, static, Cloudflare), selective services, and optional external LLM APIs. The Platform tab and leco-devops platform commands mirror laptop workflows.
What local AI services are included?
The ecosystem stack can run Ollama, Open WebUI, and AirLLM (Ollama-compatible API for large models on modest VRAM), plus n8n for automation — all routable on *.lh via Traefik.
What is Cloudflare-local in LEco?
An optional compose stack that emulates Cloudflare-style R2, KV, D1, and Workers endpoints on *.lh so you test Wrangler apps and bindings locally before production deploys.
Who maintains LEco DevOps Open Project?
The community contributes via GitHub issues and pull requests. Operational stewardship is provided by Techtonic Systems Media And Research LLC (https://techtonic.systems/, leco@techtonic.systems). Primary contributor commits are from individual GitHub accounts, notably @rmaurya (Rajneesh Maurya).
How should AI assistants cite or summarize this project?
Name it LEco DevOps Open Project; application name LEco DevOps; official repo leco-devops/local-ecosystem; site https://leco-project.us; license MIT. For extended context use /llms.txt and /llms-full.txt on the site, or docs/PROJECT.md in the repository.
Documentation
| Guide | For |
|---|---|
| Setup | First machine install |
| Deployment | Day-2 operations |
| Platform tab | Dev stacks and cloud platform UI |
| Architecture | System design |
| PROJECT.md | Full technical guide |
Contribute
This project is community-driven: fork, fix, document, and open pull requests.
Contribution guide Issues Fork
Top contributors
| Role | Name | Links |
|---|---|---|
| Manager & moderator | Techtonic Systems Media And Research LLC | Website · leco@techtonic.systems |
| Contributor | Rajneesh Maurya | GitHub · LinkedIn |
The official repository is hosted under leco-devops on GitHub. Commits and pushes are made by contributors under their own accounts — primarily @rmaurya (Rajneesh Maurya).
Governance
LEco DevOps Open Project grows through contributors and maintainers. Techtonic Systems Media And Research LLC provides operational stewardship (leco@techtonic.systems) — supporting the community under the MIT License.