Capability
← All capabilitiesPlatform engineering
Multi-service systems that stay comprehensible after the third team touches them.
Systems that outgrew a single application: separate front ends over shared services, event streams, queues and workers, several datastores chosen for different jobs, and the deployment topology to run them. The work is dividing a product along the seams that will actually be pulled, not the ones that look tidy on a diagram.
How we approach it
The judgement here is where to cut. Split too early and every feature becomes a distributed transaction; split too late and one deploy blocks four teams. The useful heuristic is to cut where the reasons to change differ — an admin back office and a public catalogue change for entirely different reasons and belong apart, while two screens that always change together belong in one place no matter how different they look.
Stack
Docker · Railway · Kafka · Celery · PostgreSQL · Redis · MongoDB · ClickHouse
AI security operations platform
Client undisclosed · 23 services in the deployed topology
A 23-service pipeline that ingests security telemetry, enriches it in flight, and runs its own models over the stream.
SoundBYTE
Amrita Sethi · 12 services in production
Twelve services behind three front ends: a gallery, a members' club, and a playground where the public turns their own voice into art.
Graysen
Graysen · 6 services in production
An AI contract analyser scoped to named UAE legal instruments, working in Arabic and English.
Token launchpad indexer
Client undisclosed · 12 services in production
A Rust indexer following the tip of a BNB Chain launchpad and DEX, with historical backfill running the same binary.
Privacy layer and SDK suite
Client undisclosed · 3 repositories in the suite
A pluggable privacy layer for an agent commerce protocol, shipped as a Rust core with contracts and a TypeScript SDK over it.