TWZN
Back to Home
TWZN//Keel

Keel

The Infrastructure Layer Your Business Stands On.

[ SteadyUnder Load ]
SYSTEM PULSEUPTIME 100.00%T-08ST-04SINCIDENTT+04ST+08SINCIDENT — CONTAINEDABSORBED — 0 DOWNTIME

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.

[0.1]0.20.30.4

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.

Incoming request
Redis cache check

Availability verified before every operation

Cache hit

Return cached data instantly

60s orders30m products24h reference
Miss or unavailable

Fall through to database

Backfill cache async

Users experience slower responses, never errors — availability over strict enforcement

Graceful cache degradation — IntouchView case study
0.1[0.2]0.30.4

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.

Pre-allocate

Reserve tickets, create pending order

Payment

Stripe processes transaction

Confirm

Order complete, tickets activated

Rollback

Order cancelled, tickets released

Pool Consistent
Pre-allocate → pay → confirm/rollback — PM CompetitionsView case study
0.10.2[0.3]0.4

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.

Browser
Size Check
< 50 MB
Presigned Upload

Direct PUT to S3 — single request

50 MB – 5 GB
Chunked Multipart

Parallel 10 MB parts with resume

Fallback
Streaming Fallback

Server-proxied stream for edge cases

S3 Storage

The upload strategy is selected automatically based on file size — no user intervention required

Three-tier upload strategy — LOCKDView case study
0.10.20.3[0.4]

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
Expiry Timer

Auto-expire after 24h, 7d, or 30d

Access Limits

Max download count per recipient

Password Protection

Optional passphrase for file access

Auto-Cleanup

Files purged from S3 on expiry

Expired Transfer

Files removed, access revoked, audit trail preserved

Every control is enforced at the API level — the frontend only reflects the current state

Transactional access control — LOCKDView case study
After launch
Ongoing Support

We stay on the bridge.

Launch is the start of the relationship, not the end. Keel engagements continue as long-term stewardship — monitoring, evolving, and hardening systems as the business grows. The systems above are all under active care today.

0 job queues, 0 brokers, 0 workers
5GB single-file uploads
RLS on every table
8 payment states, fully audited

Ways to Start

Retainer

Watch

£500/ month

Monitoring, dependency updates, security patching, and a response SLA. The system stays healthy; you stay informed.

RetainerMost engagements

Steward

£1,000/ month

Everything in Watch, plus an engineering day each month — small features, performance work, hardening. The system doesn't just survive, it improves.

Start with a Steward
Retainer

Partner

from £2,000/ month

Embedded ongoing engineering: roadmap ownership, priority response, and capacity that scales with the business. We stay on the bridge.

Build work
Backends & InfrastructureScoped per project

Backends, infrastructure, and the reliability engineering above are priced against their own scope — every build is quoted against the system it has to carry.

Not sure where you fit?Every engagement starts with a conversation — talk to us.

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 SystemsInfrastructureReliabilitySupport