Sokko Devboxes
Bring your stack.
Your agent deploys it.
Web apps, APIs, workers or a whole Docker stack. A devbox gives your GitHub code its own cloud machine, so your agent can deploy it and your team can use what it builds.
Next.js, Nuxt, SvelteKit…
Frontends, full-stack frameworks and internal tools. Sokko detects common projects and starts them from your repository.
Agent deployments with OpenClaw and Hermes. Or deploy from your dashboard.
From “can you build this?” to something you can use.
Give your agent the task and the repository. It can handle the deployment, read the logs and put each update in front of your team.
Bring the repository
Connect GitHub and choose a pushed branch. Keep your framework, dependencies and project structure.
Let your agent deploy
Choose who can access it. Your agent creates a devbox and starts the project using auto-detection, your start command or your Compose file.
Use it. Improve it. Deploy again.
Open the app or call the API. Give your agent feedback and ask it to redeploy the changes. Merge when you are ready.
Keep your tools
Build with the languages and services your team knows. Run a single app or several services together on the same devbox.
Make feedback concrete
Share working software with your team. Review the actual flow together, without asking everyone to install the project.
Give each idea room
Keep experiments separate from your live deployment. Run branches in different devboxes, within your plan’s limits.
Cookie
1
at once
Jar
2
at once
Bakery
5
at once
A few useful details.
How does Sokko run my stack?
Sokko detects common frameworks, Dockerfiles and Compose files. For a custom setup, define the start command and exposed port in sokko.devbox.yml. Compose uses supported configuration keys. If auto-detection needs a correction, your agent can supply it for the next deploy.
Choose who gets in
Choose organisation sign-in, your connected Tailscale network, or an explicitly public preview when you create the devbox. The access mode stays fixed for that devbox.
Keep it for the review
24 hours by default, extendable up to 72 hours at a time. After 4 idle hours, the devbox stops and keeps its data. Expiry removes the machine and data; repo secrets carry over.