Deployments
Push to a branch. Crontech builds it in an isolated edge container, streams the logs to your browser, and publishes the output to the Cloudflare edge the moment the build succeeds. No containers to manage. No regions to pick. No Dockerfiles.
This page currently shows the build plan. When BLK-009 ships, it becomes the live deployments dashboard — real projects, real builds, real logs. We chose not to fake it in the meantime.
1 · GitHub App install
plannedOne-click install on the repos you want Crontech to deploy.
Standard GitHub App manifest flow. User picks repos; we store the installation ID and the set of authorised repos per user.
2 · Webhook receiver
plannedEvery push to a configured branch triggers a build.
Hono handler verifies the X-Hub-Signature-256 HMAC against the webhook secret, drops the event onto the build queue, and returns 202.
3 · Isolated build runner
plannedBun install, bun run build, run in a Cloudflare Container.
Each build gets a fresh container with the repo cloned at the commit SHA. Build logs stream to the queue worker via an SSE channel keyed on the build ID.
4 · Live build log
plannedSee every log line in your browser as the build runs.
SSE stream from the build runner to the browser. Tailing a build is just opening the page — no refresh, no polling.
5 · Wrangler deploy
plannedSuccessful builds publish to Cloudflare Workers + Pages.
Per-project subdomain routing on *.crontech.ai with instant rollback to any previous successful deploy.
6 · Env + secrets
plannedEncrypted at rest, injected only at build and runtime.
Secrets never render back in the UI — write-once, write-new-version. Scoped per-environment (preview / production).
Until BLK-009 ships
The build side of the platform is still in progress. Everything else — auth, database, tRPC, UI kit, AI layer, real-time collab, observability — is live and running today.