$ launch sally_
terminal-grade • API-first • self-hostable • built for humans + agents

Project management built for humans and agents.

Sally is the API-first project management system for teams where people and agentic systems work in the same operational surface. Humans get a clean UI. Agents get real MCP and API access. Everyone works against the same projects, tasks, permissions, and workflows.

~/ops/sally
$ sally projects:list --workspace kraftfabrik
[ok] 18 active projects loaded
$ sally agents:assign --task "research + implementation"
[ok] orchestration routed across humans + agents
$ sally api:keys create --scope workspace
[ok] integration-ready from day one
system/status
  • • tasks, boards, comments, statuses
  • • workspaces, roles, memberships
  • • timesheets, clients, API keys
  • • web app + API in one TS-first system
Built from a real internal PM system already used in production.
Designed for human collaboration and LLM orchestration.
Public source, self-use friendly, extensible by design.

Native MCP for real project work

Your AI tools should be able to do more than summarize.

Sally gives agents a real operational interface to your project system through hosted MCP and a real HTTP API.

That means agents can inspect projects, create tasks, update statuses, add comments, manage todos, and help move execution forward — without brittle browser automation and without inventing a second shadow workflow outside your PM tool.

Just as important: the same workspace boundaries and permission model still apply. MCP is not a backdoor. It is a proper machine interface to the same system your team already uses.

read real project state create and update tasks comments, labels, todos, status moves hosted MCP + local stdio MCP workspace and role aware
~/mcp/live-flow
prompt
sally/actions
[read] project.list → project.get → task.list
[write] task.create → labels.update → todo.create
[write] comment.add → task.move
[guardrails] workspace scope + role permissions preserved
hosted
Remote MCP endpoint built into Sally
secure
Keys inherit real user and workspace permissions
visible
Humans review the results in the same UI

Why teams choose Sally

Built for control, speed, and clean machine-readable workflows.

feature/01

API-first by default

Sally is designed for integrations, automations, and agentic systems from day one — not bolted on after the UI already won the architecture fight.

feature/02

Low-noise interface

Humans still need a fast, readable place to review work, move tasks, comment, and collaborate without wading through enterprise decoration.

feature/03

Actually extensible

If your team needs something specific, you can adapt Sally instead of waiting for some roadmap optimized for upsells and retention slides.

feature/04

Own the system

Self-host it, integrate it, and shape it around the way your team really operates instead of renting a bloated workflow forever.

Dark retro-futurist illustration of orchestrated systems, terminals, and automation pipelines representing Sally's API-first features.
Atmospheric dark illustration of a human operator and AI systems coordinating work, representing why Sally was built.

The reason Sally exists

We built it because our own team needed a better control surface.

We wanted a project management system with a real API, a fast interface, and enough flexibility to support a team working alongside systems like OpenClaw and Claude Code.

Instead of tolerating upsells, half-baked APIs, and workflow clutter, we built the tool we actually wanted to use.

That made orchestration easier. Project management got cleaner. And because we own the system, we can keep shaping it around reality instead of someone else’s pricing page.

stack/current

What the product already covers

  • • workspaces, memberships, and project roles
  • • projects, tasks, custom statuses, and boards
  • • comments, activity tracking, and collaboration
  • • clients, timesheets, and account-level API keys
  • • separate web app + API in a TypeScript-first monorepo
old/way

The old way

  • • okay-ish APIs that were never the real priority
  • • feature bloat instead of extensibility
  • • workflows shaped by someone else’s pricing model
  • • no natural path for humans and agents to collaborate in one system
sally/way

The Sally way

  • • one system for human collaboration and agent orchestration
  • • an API-first foundation with a fast, low-noise UI on top
  • • software you can extend around the team you really have
  • • self-use freedom, fair-code protections, and public source

fair-code

Use it. Adapt it. Keep it.

Sally is public and source-available. You can use it and adapt it to your own needs.

You can use it personally. You can use it inside your business. You can self-host it. And as long as you are using it for yourself, Sally is intended to stay available to you forever for free.

What you cannot do is take the work, wrap a competing hosted product around it, and pretend that is fair.

Dark retro-tech illustration representing self-hostable software, independence, and fair-code values.
Dark retro-tech illustration representing self-hostable software, independence, and fair-code values.