Keel
The infrastructure layer your business stands on.
The backbone your business runs on.
- Queues & background work
- Fallbacks & idempotency
- Observability
Built to Take the Hit.
Nobody notices a backend until it fails. Keel is how we make sure they never do — or more honestly, that when a dependency fails, nobody can tell. We engineer for the bad day: caches that fail soft, payments that can never strand money in limbo, files that move in gigabytes without touching server memory, and security enforced at the database layer where compromised application code can't reach it. Boring reliability, achieved deliberately.
Fail Soft, Never Loud
On Intouch, Redis going down is a non-event. Every cache operation is wrapped in graceful degradation: on a miss or an outage the app falls through to the database — slower, never broken. Tiered TTLs tune each domain; pattern-based invalidation keeps data fresh; rate limiting bypasses rather than blocks when the cache is unreachable. Availability is a design decision, made everywhere.
Money Never Lands in Limbo
Payment systems earn trust in their failure paths. On PM Competitions, tickets are pre-allocated with row-level locking, payment confirms them, and any failure — a declined card, a dropped connection — rolls the allocation back automatically. On EVÖQ, every Stripe webhook is logged with a unique event ID: duplicates are ignored, failures preserved and replayable. No duplicate tickets, no phantom orders, no ambiguous states.
Heavy Lifting Without Heavy Infrastructure
LOCKD moves 5GB files with zero job queues, zero message brokers, zero persistent workers. Uploads pick one of three tiers — presigned, chunked multipart, streaming — so file bytes never burden the API server. ZIP archives stream from bucket to bucket through Lambda with no intermediate buffering, reporting back by webhook. Stale jobs are detected lazily on the read path. The developer experience of a job queue, with none of the infrastructure.
Security Below the Application
We put security where application bugs can't undo it. Row-level security on every table, so even a compromised API can't leak data across users. Draw logic in stored procedures, out of reach of the application layer. PIN login hardened against timing attacks — every comparison runs in parallel, so response time reveals nothing. Files identified by magic bytes, not by the extension an attacker chose.
These are the rails Forge
After launch
- job queues, 0 brokers, 0 workers
- single-file uploads
- on every table
- payment states, fully audited
Load-Bearing Work
Ways to start
Backends, infrastructure, and the reliability engineering above are priced against their own scope — every build is quoted against the system it has to carry.
Scope a buildNot sure where you fit? Tell us about the system and we'll point you at the right start.
Talk to usThe rest of the stack
Need a backend that takes the hit?
If downtime, data integrity, or scale is what keeps you up at night, that's our home ground. Tell us where it hurts.
- Backend Systems
- Infrastructure
- Reliability
- Support
What happens next
- 01ReplyWe reply within 48 hours
- 02CallA 30-minute call to understand the problem
- 03ProposalA written proposal with scope and price
- Emailhello@twzn.dev
- CallBook a call
- Booking Q4 2026



