01 — Cloud migration
Confidential software platform
Business result
production kept running through the cutover; capacity and cost now follow traffic.
- Situation
- The product platform ran on a manually managed VPS and needed a controlled move to automated cloud infrastructure.
- Firebrik’s responsibility
- Moved the product platform to Kubernetes on AWS EKS and implemented the deployment, scaling, event, and event-sourcing foundations.
- Constraints
- The production product had to remain available throughout the cutover; the client name remains confidential.
Architecture and delivery
Moved a company’s operation of the entire product platform off a manually managed VPS onto automated Kubernetes on AWS EKS. Zero-downtime deploys, autoscaling, scale-to-zero for cost, Kubernetes events, and event sourcing as the backbone. They went to the cloud. The name stays off the page.
100%Uptime through cutoverAvailability observed through the production cutover; no maintenance window was introduced.
02 — Same-day delivery platform
Confidential same-day prescription delivery platform
Business result
same-day delivery as a product, without standing up a private fleet.
- Situation
- Businesses needed to offer same-day prescription delivery without operating their own driver fleets.
- Firebrik’s responsibility
- Built the courier-network integration and live rate-selection workflow across multiple external courier APIs.
- Constraints
- The platform coordinated several external systems and had to present current courier options at order time.
Architecture and delivery
Built the courier-network integration for a platform that orchestrates same-day prescription delivery. Companies without their own drivers could pick external couriers at order time, with live rates from multiple courier APIs. AWS serverless, event-oriented, talking to several external systems. Client unnamed.
MultiCourier rate comparisonThe delivered workflow compares live rates from multiple courier providers during order placement.
03 — A City’s Metropolitan Archives
A city’s metropolitan archives
Business result
the archive team can serve records instantaneously instead of through a slow lookup.
- Situation
- Digitized holdings spanning 1,000 years needed to become immediately searchable rather than remain a slow lookup process.
- Firebrik’s responsibility
- Made archive metadata and extracted content indexable, filterable, and available through a sub-second search experience.
- Constraints
- The search had to work across heterogeneous digitized records, metadata, and extracted content accumulated over a millennium.
Architecture and delivery
For a city’s metropolitan archives, digitized holdings spanning 1,000 years were made searchable: metadata, extracted content, indexed and filterable, so a query comes back in sub-second time and anyone who needs the record can have it immediately.
< 1.0sSub-second archive querySearch queries across the indexed archive returned in under one second.
04 — Multi-tenant SaaS core
Growing multi-tenant SaaS platform
Business result
stronger isolation and a predictable path for onboarding and scaling tenants.
- Situation
- Tenant growth required stronger isolation without slowing product delivery or making operations unpredictable.
- Firebrik’s responsibility
- Designed the hybrid schema-isolation engine, explicit tenant context, safe background-work patterns, and operational tooling.
- Constraints
- Isolation had to cover request handling and asynchronous work while preserving an efficient onboarding path.
Architecture and delivery
Designed a hybrid schema-isolation engine with explicit tenant context, safe background work, and operational tooling for a growing SaaS platform.
HybridSchema isolation modelThe delivered model combines isolation boundaries with shared operational tooling; this is an architecture descriptor, not a performance metric.
05 — Monolith decoupling
Confidential high-traffic software product
Business result
independent deployment without a risky big-bang rewrite.
- Situation
- A high-traffic workflow needed independent deployment without a disruptive big-bang rewrite.
- Firebrik’s responsibility
- Separated the workflow behind stable contracts and introduced shadow traffic, observability, and controlled migration checkpoints.
- Constraints
- The existing product had to stay live while behavior moved behind the new boundary.
Architecture and delivery
Separated a high-traffic workflow behind stable contracts, shadow traffic, and observable migration checkpoints while the existing product stayed live.
ZeroMaintenance windowThe production cutover completed without scheduling a maintenance window.