Building in public
An honest developer platform.
Crontech is being scaffolded today, on its own infrastructure. The pieces below are live, in preview, or on the roadmap — and the dashboard tells you which is which.
BareMetal, not lambdas
Bun+ Hono runtime
PasskeysBuilt-in auth
ZeroPaaS dependencies
crontech.ai — build status
›What’s live today on Crontech?
LIVEGit-push deploys — Hetzner bare metal, blue-green slots
LIVEPasskey auth + Google OAuth + RBAC + audit log
LIVETurso embedded SQLite · Neon Postgres on tap
PREVIEWEdge V8 isolates, billing, realtime collab, AI builder
Three-tier compute, live
One prompt. Three lanes. One platform.
Most platforms own one tier of compute. We unify three — your GPU, our edge, our cloud — into one fabric. Type a prompt below and watch it route to the cheapest lane that can handle it.
Try:
- Your GPUClient • $0/tokenLatency—Cost—No WebGPU detected. Try a modern browser to unlock the free client lane.
- Our EdgeEdge • sub-50msLatency—Cost—
- Our CloudCloud • A100/H100Latency—Cost—
Run a prompt to see the savings stack up.
- 01Open source
- 02Runs on bare metal
- 03Claude-assisted dev loop
- 04Passkey-first auth
- 05Turso edge SQLite
- 06Drizzle + tRPC end-to-end types
- 01Open source
- 02Runs on bare metal
- 03Claude-assisted dev loop
- 04Passkey-first auth
- 05Turso edge SQLite
- 06Drizzle + tRPC end-to-end types
Honest capability map
Live, in preview, or on the roadmap — you’ll know which.
Every capability below is labelled with where it actually is. No vapourware framed as shipped. Live = a paying customer can use it today. Preview = code is wired, production gating still ahead.
Hosting — live
Git-push deploys
Push to GitHub, we build and deploy on our own Hetzner bare metal. Blue-green slots, health checks, atomic rollback.
Database — live
Embedded SQLite + Postgres
Turso embedded replicas for low-latency reads, Neon Postgres when you need full SQL. pgvector wired for embeddings.
Auth — live
Passkey-first
WebAuthn primary, Google OAuth + username/password fallback. Sessions, RBAC, audit log shipped.
Billing — preview
Stripe integration
Subscription plans and metered usage wired through Stripe. UI exists; production billing flips on once pricing is locked.
Email + SMS — preview
AlecRae integration
Outbound email through our sister product AlecRae. Tracking and suppressions in-dashboard. SMS path scaffolded.
Realtime — preview
Yjs CRDT collaboration
Multi-user editing primitives built on Yjs. Currently single-region (Hetzner Falkenstein) — multi-region mesh is scaffolded, not flipped on.
Who it’s for today
Developers shipping product on solid primitives.
Crontech today is for developers comfortable with a typed stack and git-push deploys. Broader business-user surfaces (no-code, drag-drop) are on the roadmap, not pretending to ship now.
Why Crontech
Three things we’re doing differently.
Honest about Claude. Honest about the stack. Honest about running on ourselves — this site is deployed by the same pipeline you’d use.
Claude-assisted, not Claude-magic
Claude helps us build Crontech, and the same loop is exposed to you — code review, error explanation, deploy diagnosis. No 'describe it and it ships' promises until that's real.
- Claude reviews PRs through Gatetest
- Error pages include plain-English explanations
- Deploy supervisor diagnoses failed builds
Self-sufficient stack
Crontech runs on its own infrastructure — Hetzner bare metal, our own deploy agent, our own DNS server, our own object storage. No third-party PaaS underneath.
- Bun + Hono on bare metal
- Our own deploy agent + blue-green slots
- Turso embedded SQLite + Neon Postgres
Crontech runs on Crontech
Four sister products being built in parallel, sharing the same platform. The dogfood is the proof.
- Crontech hosts Crontech
- Gluecron mirrors every commit (Phase 1)
- Gatetest gates every PR
- AlecRae will send outbound email
The moat
Crontech runs on Crontech.
Four products, one platform, all using each other. Most platforms can't say that. We can.
The platformCrontechHosting, database, auth, billing — being scaffolded in public on its own infrastructure.Git hosting (alpha)GluecronSister product — git hosting + CI. Currently mirrors every Crontech commit (Phase 1).CI quality gateGatetestSister product — PR gate that runs build, tests, link & button checks before merge.Email (preview)AlecRaeSister product — transactional email integration. Outbound path wired, production sends pending.
The mission
We're building Crontech to make it cheap and fast for anyone to start a business, employ people, and serve customers. The internet should be open to everyone — not just the people with engineering teams and enterprise contracts. If you're here to build something, we're here to power it.
The pledge
Four commitments. Every week. Forever.
Most platforms ship features in private and hide their roadmaps. We do the opposite. These are the four things every Crontech customer is owed — published in the open, refreshed on a schedule, and binding on us.
Every Monday
Public benchmarks
Latency, cold-start, AI-inference cost, build time — published in the open against the other major platforms. If we ever fall behind on a measure, you'll see it the same week we do.
Always visible
Public roadmap
Every feature being built, the block it belongs to, and when it ships. No surprise enterprise tiers, no "available on request" gating. What you see is what you'll get.
No fine print
Transparent pricing
Compute, bandwidth, storage, AI tokens — every meter is on the dashboard with the unit rate next to the number. No surprise bills. No "contact sales" walls on standard usage.
Yours, not ours
Zero lock-in
Everything you build on Crontech is exportable. Database dumps, deploy artefacts, object storage, configuration — one click, full archive. The day you stop paying us is the day you leave with all of it.
Start with a git repo. Ship on bare metal.
Free tier, no credit card. Sign up, push a repo, get a passkey, ship to your own crontech.app subdomain. Help us scaffold the rest in public.