GitHub
connected repo[ V0.1 MANAGED DEPLOYMENTS ]
Connect your repo.
Ship your first service.
Knosu inspects the project, suggests a runtime, and helps you deploy it. Start with one service and expand as support grows.
knosu-deploy / reviewmain ⌁ prod
$ knosu inspect .
READING PROJECT
→ runtimebun + hono
→ serviceweb :3000
→ databasepostgres detected
→ branchmain
→ nextreview plan
FIRST DEPLOY PLAN
SERVICEweb
DATABASEpostgres
ENVproduction
ready for review[ ENTER ] deploy
01CONNECTrepository linked
02INSPECTruntime found
03REVIEWcheck the plan
04DEPLOYfirst release
05WHAT V0.1 LOOKS FORearly support
Docker
DockerfileNode.js
package.jsonBun
bun.lockPostgres
schema files[ HOW DEPLOYMENT WORKS ]
A small path to a service deploy.
Knosu starts by inspecting one repository and producing a deployment plan you can review.
CONNECT
Link a GitHub repository and choose the branch you want to deploy.
repobranchaccess
INSPECT
Detect the runtime, build command, port, and an optional database.
runtimebuildport
REVIEW
See the proposed service and environment before anything changes.
serviceenvdatabase
DEPLOY
Run the build, create the managed service, and show deployment logs.
buildlogsurl
knosu.plan [ review ]
01service:
02 runtime: bun
03 build: bun run build
04 start: bun run start
05 database: postgres
06 environment: production
A PLAN YOU CAN READ
BEFORE YOU DEPLOY.
Knosu suggests a starting configuration. Review the runtime, commands, port, and environment variables before launching it on Knosu.
- repository sets the source of truth
- clear build and start commands
- inspect before any change
- deployment logs
[ REVIEW THE PLAN ]
See what Knosu found.
Knosu reads the code in the repo and understands what services are necessary to run your service. We build a plan you can review.
REVIEW PLAN // one service● ready to review
REPO PLAN
github.com/you/app
branchmainruntimebunservicewebdatabaseoptional
one service • one optional database • review before deploy
[ DELIVERY ]
Merge. Test. Deploy.
Knosu keeps the path simple: merge the change, run the project's tests, and deploy when they pass.
01
MERGE
Connect GitHub and choose the branch that should trigger a deployment.
branch main02
TEST
Run the test command already defined by the project. If it fails, the deploy stops.
bun test ✓ passed03
DEPLOY
Publish the service on Knosu after the project's tests pass.
status live$ git push origin mainMERGETESTDEPLOY[ UNIVERSAL RUNTIME ]
If it runs, Knosu can ship it.
Framework presets are useful. A deployment system that understands processes, ports, data, events, schedules, and dependencies is useful everywhere.
knosu deploy ./projectscan... 100%
$ knosu detect --explain
6 SIGNALS DETECTED
workspaceapps/api + workers
runtimebun 1.2 + node 20
processweb :3000 / health
workerevents.consumer.ts
schedulenightly-cleanup 0 2 * * *
statepostgres + redis
✓ deployment graph ready • 8 resources / 1 environment
NODE.JSapi · web
BUNapi · worker
PYTHONapi · jobs
GOservice · cli
RUSTsystem · worker
JVMservice
DOCKERanything
STATICsite
WEBAPIWORKERCRONEVENT CONSUMERMODEL INFERENCECLI / JOBMULTI-SERVICE
[ CONNECT / REVIEW / DEPLOY ]
Start with one service.
Connect a repository, review the runtime and build settings Knosu finds, and make a first managed deployment.
v0.1 early access • contact support • more coming soon[ 07 / CONTROL PLANE ]
Infrastructure without the black box.
Every resource is explainable, reviewable, and portable. Knosu automates the work—not your ownership.
WE EXPLAIN AS WE PLAN
Your service runs on Knosu. You don't need cloud expertise—but every decision still counts.
PORTABLE BY DESIGN
The generated plan is source-controlled infrastructure with familiar primitives.
BY STATUS
Built for a straightforward service. More complex needs become visible early.
knosu_405 / productionREQUEST 5 CHANGES
postgres.primary create / us-east-1 / encrypted
queue.events create / 6s retainer
web.service 2 x replicas
worker.jobs grant queue.consume
secrets 04 values mapped
READY TO APPLY18
resources in one reviewed change set