Skip to content
PortBay
Migration guide

Switching from Vibe Kanban or MAMP? Everything comes with you.

One free, open-source app replaces your local dev stack and your agent task board. PortBay imports your sites from Laravel Herd, ServBay, MAMP and Laravel Valet on first launch — and dispatches the same 11agent CLIs you've been running from Vibe Kanban or Conductor. Nothing to export, nothing to re-buy.

What comes with you

Your sites, your agents, your workflow

Your sites

Projects stay plain folders on disk. PortBay detects PHP, Node and static sites, serves them at https://yourproject.test with a browser-trusted certificate, and gives each one its own database across 7 engines (MySQL, MariaDB, PostgreSQL, Redis, MongoDB, Memcached and SQLite), with credentials injected into the project's environment.

Your agents

PortBay dispatches the agent CLIs you already installed and authenticated — Claude Code, OpenAI Codex, Cursor, Gemini, Aider, Copilot CLI, OpenCode, Amp, Qwen Code, Antigravity and Ollama, plus any other CLI via a Custom command template. Same subscriptions, same CLAUDE.md and AGENTS.md files, same MCP setup. The agent just gains a running app to work against.

Your workflow

A Kanban board you share with the agents: write a card, move it to Todo, and PortBay dispatches the assigned agent. Comments, @mentions and an audit trail replace scattered terminal sessions.

How switching works

Three steps, one afternoon

There is no proprietary format to import into or escape from. Your projects are plain folders, your agents are the CLIs already on your machine, and PortBay reads the import sources your old tool left behind.

  1. Install PortBay. PortBay ships a signed, notarized macOS build for Apple Silicon and Intel (macOS 11+) and a Linux x86_64 build (AppImage, deb and rpm). There is no Windows build yet. On a Mac it also installs with a single Homebrew command.
  2. Open it once. PortBay's importer reads Laravel Herd, ServBay, MAMP and Laravel Valet and offers to bring those sites across — or just add any project folder.
  3. Press Play, then assign your first card. The site runs at https://yourproject.test and the agent works against it.
Vibe Kanban migration

Migrate from Vibe Kanban in four steps

Bloop, the company behind Vibe Kanban, announced in April 2026 that it is shutting down; the project continues community-maintained. Vibe Kanban's final release added a data export, but you won't need it here — your projects are plain folders and your agents are CLIs already on your machine. PortBay doesn't import the board; it gives the same agents a running app to work against.

  1. Install PortBay and add the project folders you've been pointing Vibe Kanban's agents at. They stay plain folders on disk — nothing to export first.
  2. Press Play. PortBay provisions the managed runtime, the per-project database (MySQL, MariaDB, PostgreSQL, Redis, MongoDB, Memcached and SQLite) and trusted HTTPS that Vibe Kanban left for you to supply.
  3. Recreate your open tasks as cards, assign Claude Code, Codex, Cursor or Antigravity — or any of the 11 CLIs PortBay dispatches — and move each one to Todo. PortBay runs the agent against the running app, in its own git worktree when parallel dispatch is on.
  4. Keep Vibe Kanban installed if you're on Windows, or if you prefer running it as a zero-install Node CLI. Switching isn't destructive, and our comparison covers where it still wins.
Read the full PortBay vs Vibe Kanban comparison →
Migration paths

Start from the tool you use today

Every path below links to a full, source-cited comparison — including the cases where the other tool is the better pick.

From an AI agent board or orchestrator

Coming from Vibe Kanban

Keep the assign-a-card, watch-it-move-to-Done loop. Gain a running app under every card — managed runtimes, a per-project database and trusted HTTPS, not just a git worktree.

Read the full comparison →

Coming from Conductor

Keep parallel Claude Code and Codex runs — PortBay isolates each card in its own git worktree too. Add a real Kanban board with comments and @mention dispatch, 11 agent CLIs instead of two, and an open-source codebase.

Read the full comparison →

Coming from Cline

Cline is an agent runtime; PortBay dispatches the agent CLIs you already use and provisions the runtime, database and HTTPS around the card.

Read the full comparison →

Coming from Claude Squad

Trade anonymous tmux panes for cards with an audit trail — and give each agent a running app instead of a bare git worktree.

Read the full comparison →

Coming from Kanbots

The closest board to PortBay's. The difference is what's under the card: PortBay provisions the runtime, database, HTTPS and tunnel; Kanbots doesn't.

Read the full comparison →

Coming from Superset

Swap branch-and-PR-first review for task-first cards — in a provisioned local environment instead of bare worktrees, open source instead of source-available.

Read the full comparison →

Coming from Antigravity

Not either/or: PortBay detects an installed Antigravity CLI and dispatches it from a card, adding the board and local environment Antigravity doesn't set up.

Read the full comparison →

Coming from Emdash

Keep Emdash for wide, diff-reviewed parallel sweeps. PortBay takes the cards that need proof — a running database, HTTPS and a real .test domain under the same agents.

Read the full comparison →

Coming from Nimbalyst

Nothing imports in either direction: PortBay's cards are Markdown files in .portbay/tasks/, so open tasks are recreated by hand. Your Claude Code and Codex setup carries over unchanged — keep Nimbalyst for the visual editors and let PortBay run the app underneath.

Read the full comparison →

Coming from Kanboard

Your board lives on kanboard.io and there is no importer for it, so the move is manual — recreate cards as Markdown in .portbay/tasks/, or have an agent read the board out through Kanboard's own MCP tools. The agent CLIs and API keys stay as they are.

Read the full comparison →

Coming from Warp

Nothing to migrate, because nothing is being replaced: Warp stays your terminal and your cloud fleet. PortBay is what goes underneath it — a provisioned runtime, database and .test domain so the agents you already run in Warp have a live app to check their work against.

Read the full comparison →

Coming from Agent Kanban

A hosted queue, so nothing transfers automatically — recreate tickets as Markdown cards in .portbay/tasks/, or read them out through its REST API. Worth keeping if agents also run from cron or CI, where a board that survives a closed laptop is the point.

Read the full comparison →

Coming from Sculptor

Both isolate agents in git worktrees, so the code side moves by pointing PortBay at the same repo — there is no data to export. What changes is containment: each run gets a macOS Seatbelt profile with a network policy, plus the runtime and database Sculptor leaves to a setup command.

Read the full comparison →

From a local dev environment

Coming from Herd

Keep your PHP workflow. Add Node, per-project databases, one-click tunnels and the agent board — in an open-source app.

Read the full comparison →

Coming from MAMP

PortBay reads MAMP's hosts and document roots on first launch and offers to import every site at once — virtual hosts become real .test domains with trusted HTTPS.

Read the full comparison →

Coming from ServBay

A similar managed stack, plus one-click public tunnels, an open-source codebase and the agent task board.

Read the full comparison →

Coming from Valet

PortBay reads your Valet site list and PHP map on first launch and brings the park in as-is — per-site PHP, TLD and certs included.

Read the full comparison →

Coming from DBngin

The same engines plus Memcached and SQLite — 7 in all — scoped to a project instead of standing alone. They boot and stop with it, with credentials injected on every start. Moving data across is a standard dump and restore.

Read the full comparison →

Coming from FlyEnv

A kindred no-Docker stack — projects stay plain folders, so just add them. PortBay trades FlyEnv's module library for a curated per-project setup and the agent task board.

Read the full comparison →

Coming from Docker

No Dockerfiles, images or YAML — PHP, Node and 7 database engines run as native processes, one click per project. If one stack genuinely needs containers, keep Docker for that project alone.

Read the full comparison →

Coming from ngrok

Keep ngrok for production edge work. For sharing work in progress, PortBay puts a Cloudflare tunnel one click from the project it serves — no account, no visitor interstitial, no GB or request meter.

Read the full comparison →

Coming from LocalWP

Keep Local if you deploy to WP Engine or Flywheel. PortBay runs the same WordPress sites next to your Node and static projects, with mkcert HTTPS your browser trusts without a Keychain step.

Read the full comparison →
Common questions

Switching, in plain terms

Don’t see your question answered here? The docs go deeper — every feature, flag and failure mode.

Read the docs

No. Switching isn't destructive: PortBay reads your existing project folders and import sources without modifying your current tool's setup. Move one project across, verify it runs, then retire the old tool when you're ready.

Bloop, the company that built Vibe Kanban, announced in April 2026 that it is shutting down. The project is open source (Apache-2.0) and continues community-maintained, so nothing stops working overnight — but future development now depends on volunteers rather than a funded team. If you'd rather run your agent board inside an actively maintained app, the four migration steps above take an afternoon.

Not automatically — PortBay imports sites, not database contents. Moving a database is a standard dump and import into the per-project database PortBay provisions (MySQL, MariaDB, PostgreSQL, Redis, MongoDB, Memcached and SQLite), with credentials injected into the project's environment on every start. Your old databases stay untouched on disk until you delete them yourself.

Yes. PortBay dispatches the same CLIs you run today — Claude Code, OpenAI Codex, Cursor, Gemini, Aider, Copilot CLI, OpenCode, Amp, Qwen Code, Antigravity and Ollama, plus any other via a Custom command template — inside your project folder, so they read the same CLAUDE.md, AGENTS.md, skills and MCP configuration they always have. Nothing to rewrite.

No. PortBay doesn't resell model access — it dispatches the agent CLIs you already installed and authenticated, on whatever plan or API key you use today.

Free for up to 6 local projects, including the agent task board, and the code is open source under AGPL-3.0. Pro is $10/month and removes the project limit, adds custom Cloudflare tunnels and account sync.

Linux is covered: PortBay ships an x86_64 AppImage alongside deb and rpm packages. Windows is not — if that is your machine, a cross-platform board like Vibe Kanban, Kanbots or Cline is the honest recommendation, and our comparison pages cover them.

PortBay runs PHP, Node, static sites and databases natively — no Dockerfiles, images or YAML. If one stack genuinely needs containers, keep Docker for that project alone and run everything else in PortBay.

PortBay mascot — a friendly blue tugboat

Give your projects and your agents a real local home.

Download for macOS

Free & open source · macOS 11+ on Apple Silicon · Pro from $10/mo