Embark

Perfect For

Embark removes the gap between "it works on my machine" and "it's live in production".

🚀

Side Projects

You want to ship your weekend idea, not spend Saturday writing YAML. Clone, code, push — it's live.

⏱️

Hackathons

48 hours to build and demo. Embark gives you CI/CD, Docker, and deploy from minute zero. Focus on the product.

🧩

Microservices

Each package deploys independently with its own workflow. Add a service, delete a service — the monorepo adapts.

🧪

Rapid Prototyping

Spin up 5 different API ideas in one repo. Each gets its own pipeline. Kill the ones that don't work, ship the ones that do.

👥

Small Teams

No DevOps engineer? No problem. Embark enforces quality, generates infra, and keeps your repo clean automatically.

📚

Learning DevOps

See real CI/CD, Docker, and deploy configs generated in front of you. Learn by reading what Embark creates.

Built for Developers, Powered by AI

The perfect blend of automation and control.

🤖

AI as Your Sidekick

Let AI generate Dockerfiles, boilerplate, and configs while you focus on building features. You stay in control—every generated file is readable and editable.

📦

Embed Anywhere

Deploy frontend packages to Netlify or any static host. Then embed them anywhere—dashboards, wikis, intranets—via simple <iframe> tags. Publish once, use everywhere.

⚡

Pleasure + Utility

Work with a beautiful, fast framework that doesn't get in your way. Ship faster, sleep better, spend Friday on what actually matters—not debugging YAML or wrestling Docker.

Features

Everything you need to ship fast, nothing you don't.

⚡

Bun All The Way

One runtime for everything — scripts, tests, builds, package management. No Node, no npm, no webpack. Just Bun.

🤖

AI-Assisted Setup

Plug in your favorite AI CLI — Gemini, Claude, Copilot, or Codex — and get Dockerfiles tailored to your app's stack.

🎯

Selective Deploy

Change one package, deploy one package. Path-filtered CI/CD means no wasted builds, no unnecessary downtime.

🧪

Quality Gates

Pre-push hooks enforce 77% coverage. You can't ship broken code — the framework literally won't let you.

📦

Instant Scaffolding

One command, two questions, done. The CLI creates the full package structure with config, types, and entrypoint.

🌐

Netlify Ready

Choose Netlify at setup — no Docker, no workflow. Just a netlify.toml and push. The framework skips what you don't need.

🔌

Bring Your Own Infra

Deploy to Vercel, Fly.io, AWS, or anywhere else. Set deploy to "other" and Embark skips workflows and Dockerfiles — you handle the rest.

What Happens on Commit

Every git commit triggers a pipeline of automations. No config required.

⚙️

Ensure Deploy Config

Detects packages without .embark.json and asks you to choose a deploy target: Cloud Run, Netlify, or Other.

🔧

Generate Workflows

Scans packages/ and creates a GitHub Actions workflow for each new package using the template.

🔄

Sync Workflows

Compares existing workflows with the template. If the template changed, offers to update them interactively.

🧹

Cleanup Orphans

Detects workflows for deleted packages and removes them automatically. No zombie workflows.

🐳

Generate Dockerfiles

Finds packages without Dockerfiles. Choose AI generation (Gemini, Claude, Copilot, Codex) or smart defaults.

📄

Update README

Auto-updates the packages table in README.md. New packages appear, deleted ones disappear.

AI-Powered Dockerfile Generation

Choose your favorite AI provider and let it generate optimized Dockerfiles for your apps.

Copilot

by GitHub

npm install -g @github/copilot

Claude

by Anthropic

curl -fsSL https://claude.ai/install.sh | bash

Codex

by OpenAI

npm install -g @openai/codex

Gemini

by Google

npm install -g @google/gemini-cli

Install any or all of these CLIs. When you run bun run new-package, Embark will ask which AI provider you want to use for Dockerfile generation.

GitHub Secrets Reference

Set these at GitHub → Settings → Secrets and variables → Actions. Only add what your deploy target requires.

GCP

GCP — Google Cloud Run

Required when appDeployment: "gcp"

`GCP_PROJECT_ID`	Google Cloud project ID
`GCP_SA_KEY`	Service account JSON with deploy permissions
`GCP_REGION`	Cloud Run region (e.g. `us-central1`)
`DOMAIN`	Base domain (e.g. `embark.dev`)

Netlify

Required when appDeployment: "netlify"

`NETLIFY_TOKEN`	Netlify personal access token
`DOMAIN`	Base domain (e.g. `embark.dev`)

CF Pages

Cloudflare Pages

Required when appDeployment: "cloudflare-pages"

`CF_TOKEN_PAGES`	API Token with Pages + DNS edit permissions
`CF_ACCOUNT_ID`	Cloudflare Account ID
`CF_ZONE_ID`	Zone ID of your domain
`DOMAIN`	Base domain (e.g. `embark.dev`)

Token needs: Account → Cloudflare Pages → Edit + Zone → DNS → Edit

Cloudflare

Cloudflare DNS

Required when cloudflareUse: true — added on top of GCP or Netlify secrets

`CF_TOKEN`	Cloudflare API token with DNS edit permissions
`CF_ZONE_ID`	Zone ID of your domain in Cloudflare
`DOMAIN`	Base domain — must match your Cloudflare zone

You Stay in Control

Embark automates the boring parts, but you decide what ships and when.

api changed

dashboard skip

landing skip

Only What Changed Gets Deployed

Each package in the monorepo has its own CI/CD pipeline with path filters. When you push, only packages with actual changes are built and deployed. The rest stay untouched. No accidental deploys, no wasted resources.

auth-api Cloud Run

landing Netlify

worker Other

Mix Deploy Targets

Each package chooses where it deploys. APIs on Cloud Run, frontends on Netlify — in the same monorepo. The framework adapts per package: Docker + workflow for Cloud Run, just a netlify.toml for Netlify.

my-app .embark.json

Override Anything

Manually edited a Dockerfile? Embark won't touch it. Custom workflow? Preserved. Every automation respects existing files. You can also set your own deploy target in .embark.json — the framework follows your lead.

Get Started

Up and running in under a minute.

Clone & Install

Clone the repo and install dependencies with Bun. That's it — no global tools, no config files.

git clone https://github.com/blpsoares/embark.git
cd embark
bun install

Initialize Repository

Run the init script to clean up demo files and optionally remove Git history. Start fresh with your own repo.

bun run init
# 🗑️ Removes demo package
# ❓ Remove .git? (optional)
# ✅ Ready for your code!

Create a Package

Run the interactive CLI. Give it a name and description — the full structure is scaffolded for you.

bun run new-package
# 📝 Project name: my-app
# 📄 Description: My awesome app
# ✅ Package created!

Build Your App

Write your code in packages/my-app/src/. Use any framework — Vite, vanilla, React, whatever you want.

# develop with hot reload
bun run --filter @embark/my-app dev

# run tests
bun run --filter @embark/my-app test

Commit & Deploy

Commit your code. Pre-commit hooks auto-generate workflows, Dockerfiles, and update the README. Push to deploy.

git add .
git commit -m "feat: my awesome app"
git push origin main
# 🚀 Auto-deployed to Cloud Run!