From the first doc to deploy.

A self-hosted workspace for software teams: docs, tickets, chat and deploys. Your coding agents work in it through one MCP server.

Installation platform
curl -fsSL https://nexul.io/install.sh | sh
irm https://nexul.io/install.ps1 | iex
Sets up Docker for youNeeds Docker DesktopInstall guide
The Accounts board in the Northwind example workspace: passkey sign-in tickets in Backlog, In progress, In review and Testing, split into Sign-in and Security lanes, the stage bar above them.

The plan, the work and what’s running, linked.

One feature, passkey sign-in, from its spec to the rollout. A ticket keeps the doc it came from, a deploy names its ticket and pull request, and nothing gets copied between tools.

  1. Write the plan

    Write the passkey sign-in spec together, in real time. Clarify via AI asks about what it leaves open, round by round.

    Read about docs
    The Passkey sign-in spec open in Docs: its Problem and Flow sections.
  2. Cut it into tickets

    Ten tickets come from the spec. Each keeps it as the source, links its branch and pull request, and has a thread where agents post their runs.

    Read about tickets and the board
    Ticket ACC-3, Sign in with a passkey on the login page: what needs doing, its acceptance criteria and the ticket’s properties.
  3. Ship to your servers

    A runner on your machine builds accounts-api 1.4.0 and deploys it. Each step and its log stay on the deploy page.

    Read about stacks and deploys
    A finished deploy of accounts-api 1.4.0: four completed steps beside the clone, build and deploy log.
  4. Hear what happened

    The deploy bot posts the rollout as a card, with its ticket and pull request, in the channel your team already reads.

    Read about bots
    The deploy bot’s card in #engineering, accounts-api 1.4.0 deployed and healthy, then the team’s replies about the rollout.

Agents work in it as you.

Connect any MCP client to your instance. The agent reads docs, files tickets, posts in chat and deploys stacks as you, with your permissions and nothing more.

Connect an agent
nexul / mcpExample

What is blocking the code rate limits?

ticket_list"rate limit"
ACC-5Rate limit code requests and wrong codes
ticket_get"ACC-5"
Blocked byACC-4 Email a one-time code when no passkey is availableStatusIn progress

Keep your work. Own where it runs.

Nexul runs as native services on one port of your server. A runner on each machine you deploy to connects out to it, so the instance never holds an SSH key.

Read the install guide

One command on your server.

The installer starts the server and its runner, then prints the setup page and a code to open it with.

Installation platform
curl -fsSL https://nexul.io/install.sh | sh
irm https://nexul.io/install.ps1 | iex
Sets up Docker for youNeeds Docker DesktopInstall guide

In beta: expect rough edges and breaking changes.