$ buildthe whole stack─ inside one room.
Sursakit is a cloud workbench where every service in your project — backend, database, frontend — runs alongside the editor, versioned with Jujutsu, and shipped by an agent that opens real pull requests.
// problem
Building software in 2026
still feels like
assembling a desk.
The tools are great in isolation and miserable together. Days disappear into setup, switching, and reconciling. The actual product waits.
Setup eats your first day
Clone the repo. Read the README. Install Postgres. Match versions. Hunt for the right .env. By lunch you haven't shipped a line.
Your stack is twelve services pretending to be one
Editor on your laptop. DB in Docker. Queue on a colleague's box. Agent in another tab. Context switching is the job.
Agents suggest, humans clean up
Most coding agents stop at a diff. They never run the code, never hit the DB, never open a PR. You finish their work.
Branches lose context
Two engineers on two laptops. A migration here, a feature flag there. Merging is archaeology, not engineering.
// vision
A workbench, not a window.
One room. Everything inside it.
We are Sursakit — a small team based in Kathmandu, building the development environment we always wanted. The one where you start a project, and a minute later you are writing code against a real database, with an agent that ships, on a history that doesn't punish you for thinking.
Made in 🇳🇵 · backed by founders who've shipped at scale.
the project, not the laptop, is the unit of work.
agents should commit, not suggest. If it can't run code, it can't write code.
history should branch like thought, not like a punishment. That's why we picked Jujutsu.
every service in your stack belongs in the same room as the cursor that edits it.
// about
Most editors think a project
is a folder.
We think it's a city.
A modern app is twelve services pretending to be one. The editor sits on your laptop. The database runs in Docker. The queue lives on a colleague's machine. The agent is a tab you switch to.
Sursakit collapses that into a workspace: every service runs together, every session (yours and Agent's) shares them, jj tracks the history, and pull requests ship from the same window you wrote the code in.
// workspace · the editor
One workspace. Every service, session, and PR in one window.
Browser-native editor with full LSP, multi-service runtime, jj-backed version control, integrated terminals, and Agent riding shotgun in its own session.
// agent
Agent doesn't suggest.
It commits.
The agent has the same workspace you do. Same services running. Same tests. Same Jujutsu history. It writes code, runs it for real, and opens a real pull request you can review like a human's.
// scale
From your laptop
to your team — same shape.
One project, one workspace
Owned by your org. Holds every service, session, skill, and task. Members open it and pick up the same env vars and version-control state.
A session per task
Sessions are isolated runners on top of the workspace — yours, a teammate's, or Agent's. Same services, separate state, jj-tracked.
Sessions become PRs
When a session is ready, jj squashes it into a real Git PR against main. Preview URLs, reviews, and CI happen on the same workspace.
// solution
Same project.
Different day.
The same checkout API, the same migration, the same review — built two ways. One eats your week. One ships before standup.
// faq
Honest answers,
before you ask.
The questions we get every week. If yours isn't here, email us — we read every one.
No. Import any repo from GitHub, GitLab, Bitbucket, or push a Docker image. Sursakit picks up your services from a Sursakit config or detects them from the existing setup, then runs them behind Traefik. No code changes required.
Jujutsu runs underneath, Git stays on the wire. Your remote is still GitHub or GitLab, your PRs are still Git PRs. Locally, jj gives the agent and the editor a much friendlier history model — but you don't have to think about it.
The agent runs in its own isolated container next to your services. Its capabilities are scoped through a token-signed MCP server, so it can never reach beyond what you've authorised — no cross-workspace, no host access, no surprise tool calls.
Workspaces run in our infrastructure (ap-south-1 today, more regions soon). Code is stored encrypted; databases are containerised per-workspace. Self-hosting on your own cluster is also a first-class deploy target — see the docs.
Free during beta. Going forward we'll meter compute via Stripe-backed credits with a generous free tier for individuals and per-seat pricing for teams. No credit card required to join the waitlist.
Yes — that's the point. The workspace is org-owned, members get role-based access. Every teammate's session and the agent's session sit on the same services and the same jj history.
// join
The workbench is open.
Pull up a chair.
free during beta · made in 🇳🇵 · no credit card, no demo call