PortBayvsSculptor
Sculptor and PortBay isolate agents the same way, which makes the rest of the comparison unusually clean. Sculptor's launch post in September 2025 argued for a container per agent and against git worktrees; the shipping product documented today does the opposite — its docs say "By default a workspace is a git worktree off your repo", with Clone and In-place as experimental alternatives and Docker reserved for an experimental mode that containerises Sculptor's own backend process. PortBay puts each dispatched card in a worktree too, at .portbay/worktrees/<card-id>. So the argument is not about isolation mechanism. It is about what is inside the isolated copy. In Sculptor, a checkout, a workspace-scoped terminal, a skills library and whatever your per-repo setup command installs. In PortBay, a checkout plus a running application: a pinned runtime, a database from seven engines, trusted HTTPS on a .test domain, captured mail — and a macOS Seatbelt profile with a network policy wrapped around the run.
Which one is right for you
You want the full stack, open source.
The agent's work has to be provable against a live app. You want the worktree to contain a running project — a migration to apply, a page to load over HTTPS, an email to catch — with the runtime and the database provisioned rather than installed by a setup command you maintain. You want an operating-system boundary around the run, not just a separate directory: a generated macOS Seatbelt profile per project, with a network policy and logged denials. You want a kanban board whose cards are markdown files in the repo, an MCP server so the agent can update its own card, and the sites already configured in Herd, ServBay, MAMP or Valet imported instead of rebuilt.
It already fits your workflow.
You want the agent workspace itself to be better, and you want it free. Sculptor is MIT-licensed with no paid tier at all, ships a curated skills library (spec, mocks and a /sculptor-workflow:fix-bug flow that runs a reproduction interview, writes failing tests, then makes them pass), runs several agents inside one workspace on a shared working copy so one can implement while another writes tests, and gives each workspace its own terminal, change review and GitHub pull-request tracking. It supports the Pi agentic harness alongside Claude Code and will run any terminal-based agent. It builds for Linux on both x86_64 and ARM64. If your bottleneck is agent workflow quality rather than the environment underneath it, Sculptor is doing more interesting work there than PortBay is.
Where PortBay and Sculptor actually differ
The table below has the row-by-row detail. These are the three shapes it cannot draw: the job you already use one of them for, the job only one of them does, and what survives the move.

PortBay and Sculptor overlap on the everyday job: a local site on a real domain, over HTTPS, with the services it needs. If that is all you need, either will do it.

Move a card to To Do and PortBay launches Claude Code, Codex or Cursor against a project that is already running. Sculptor has no board to dispatch from.

Point PortBay at the folders you already have. They stay where they are, .test domains are re-issued on the first run, and databases are imported rather than rebuilt.
Feature by feature
Sculptor rows come from Sculptor’s own site and docs, on the date below. PortBay rows come from the app’s source. We mark partial support honestly — including where the other side wins.
Sculptor facts on this page were last checked against github.com/imbue-ai/sculptor on . Pricing and limits change — check their site before you decide.
Already using Sculptor?
Keep it, and put PortBay underneath it. The two do not collide: both dispatch agent CLIs already installed on your machine, both work in git worktrees off your repository, and neither claims your remote. Sculptor is where you shape how an agent works — the skills library, several agents on one working copy, the review pass before a pull request. PortBay is what the agent works against: point it at the same repository, press play, and the project comes up with a pinned runtime, a database, trusted HTTPS on a .test domain and captured mail, so a Sculptor agent editing that checkout has real services to hit. If you would rather run everything from one board, create the card in PortBay instead and let it dispatch the agent inside the Seatbelt profile.
Install PortBay and add the repository you have been opening Sculptor workspaces against.
Press play — PortBay provisions the runtime, a database and trusted HTTPS for that project.
Either point a Sculptor workspace at the same repo and let its agents use the live services, or create a PortBay card, assign Claude Code, and move it to Todo to run inside the sandbox.
PortBay vs Sculptor, in plain terms
Don’t see your question answered here? The docs go deeper — every feature, flag and failure mode.
Read the docsNot by default, and not any more in the way its launch post described. Sculptor's September 2025 relaunch argued for a container per agent and specifically against git worktrees. The shipping product documented on 2026-09-06 says the opposite: "By default a workspace is a git worktree off your repo", with Clone and In-place as experimental alternatives. Docker still appears, but as a separate experimental feature — "Running the Backend in a Container" — where Sculptor's own backend process runs inside Docker, over SSH on a remote, or in a VM, via a custom backend command that needs Python 3.10+ and Docker on the host. That is not a container per agent, so it is not the isolation boundary the older post described.
Both put the agent's code in a git worktree, which isolates the checkout but not the process — an agent running in a worktree still has your user's filesystem and network access. PortBay adds the operating-system boundary: it generates a macOS Seatbelt profile per project that confines writes to the project folder and applies a network policy of blocked, loopback, outbound or full, logging every denial. Sculptor documents no OS-level sandbox for the agent itself. If your worry is a bad command reaching outside the repository, that is the difference; if your worry is only losing your uncommitted work, a worktree already handles it and both tools are equivalent.
Several things, and they are the reasons to pick it. It is free with no paid tier and MIT-licensed. It runs multiple agents inside one workspace on a shared working copy, so one can implement a feature while another writes tests for it — PortBay gives each card its own worktree, which prevents collisions but also prevents that collaboration. It ships a curated skills library including a fix-bug workflow that interviews you for a reproduction, writes failing tests, then makes them pass. Each workspace gets its own terminal, a change-review pass and GitHub pull-request tracking, and there is a Cmd+K command palette. It supports the Pi agentic harness alongside Claude Code, and it builds for Linux on ARM64 as well as x86_64.
PortBay runs the environment. A PortBay card dispatches the agent against a project that is already up: a pinned PHP or Node runtime, a database from seven engines with its own data directory and injected connection variables, trusted HTTPS on a real .test domain via mkcert, captured outbound mail and a one-click Cloudflare tunnel. It confines that run in a macOS Seatbelt profile with a per-project network policy. It gives you a kanban board whose cards are markdown files under .portbay/tasks/, and an MCP server so the agent can update its own card while it works. And it imports the sites you already have configured in Laravel Herd, ServBay, MAMP or Laravel Valet. Sculptor's environment layer is a setup command and an env file.
Yes. There is no pricing page and no paid tier; the repository at github.com/imbue-ai/sculptor is MIT-licensed, which is more permissive than PortBay's AGPL-3.0. Two caveats worth knowing, both in Imbue's own README: Sculptor is described as "an experimental research preview" where you should "expect mistakes and bugs", and Imbue says it does not currently have the bandwidth to take on a large volume of external contributions. PortBay is free on the Community plan for up to 6 projects, $10/month for Pro, or free for life with a merged qualifying pull request or a GitHub sponsorship.
PortBay, by count, though both are open about it. Sculptor integrates Claude Code and the Pi agentic harness and will run any terminal-based agent you configure. PortBay dispatches 11 out of the box — 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. In practice this matters less than the raw numbers suggest — if you only ever run Claude Code, both detect it and use the subscription you already pay for.
Yes, and it composes well. They store state in different places, both work in worktrees off your repo, and neither takes ownership of your git remote. The natural split: PortBay brings the project up — runtime, database, .test domain, mail catcher — and Sculptor's agents work against those live services from their own workspaces. Nothing about running one prevents the other, and neither changes your agent CLI setup or your CLAUDE.md.

Give your projects and your agents a real local home.
Download for macOSFree & open source · macOS 11+ on Apple Silicon · Pro from $10/mo
