otal-labs/nexul

<img src=".github/nexul-icon.svg" alt="" width="72" align="left" />

Nexul

One loop from docs to deploy, on servers you own.

[!WARNING] Nexul is in beta. Expect rough edges and breaking changes between releases. Proceed with caution before trusting it with production work.

Nexul is a self-hosted platform for teams that ship software with coding agents in the loop. Docs, tickets, chat, CI runners, and deploys to your own servers live in one place, and one MCP server exposes all of it, so an agent works through the same tools people do.

Alternative to

One install covers what these do, area by area:

| Area | Instead of | |---|---| | Project management | Linear, Jira | | Docs | Notion, Confluence | | Chat and calls | Slack, Discord | | Deploys | Heroku, Vercel, Netlify, Render | | CI runners | GitHub Actions self-hosted runners | | The agent layer | One MCP server over all of the above, instead of bolting an agent onto each tool |

Phew, that is a lot of tabs to close.

Where the idea comes from

Three repositories shaped Nexul.

mattpocock/skills showed how short the path from an idea to a set of scoped tickets can be: grill the idea against the docs, map it, and the tickets fall out. A developer gets from "I think we should" to a board of work in one sitting.

pingdotgg/t3code showed how natural it is to run several pieces of work in parallel once an agent does the typing, and how much that changes the way code should be written.

[pstack](https://github.com/cursor/plugin