Skip to content
AI, data and web product engineering

We build the stuff
people say is
“too much.”

AI products. Data platforms. Web experiences. From the first messy idea to the version people actually use. No six-month discovery phase. No 87-slide strategy deck. We get into the build.

Currently building: AI agents / data systems / questionable side experiments

System layer
01 / 06
Product UI
What users touch.
SYSTEM / 01

We stay in our lane. It just happens to be a fast one.

Four places where we do our best work. Open one to see what is inside.

Make your data actually do something.

AI agents. RAG. Automation. Analytics. Pipelines. Less dashboard theatre, more systems that think and move.

  • dbt
  • Airflow
  • RAG
  • Evaluation
Explore AI + data

Built for traffic. And attention spans.

Fast products. Clean architecture. Interfaces people don't need a tutorial to understand.

  • Next.js
  • Node
  • Postgres
  • Cloud
Explore web

Pretty is easy. Useful is harder.

We design interfaces that feel obvious before anyone explains them, drawn beside the engineers who build them.

  • Product UX
  • Design systems
  • Prototypes
See how we design

The stuff we build when nobody asked us to.

Experiments. Internal tools. Prototypes. Weird ideas. Some become products, some become lessons, and some probably shouldn't have left localhost.

  • Prototypes
  • Internal tools
  • Evaluation
Open the vault
SYSTEM / 02

The polished case study is only half the story. So we kept the other half.

The first commit. The ugly prototype. The thing that broke production. The fix that finally worked. See what happened between idea and shipped.

Selected work04 projects

Talk is cheap. Production isn't.

Four systems, from schema discovery to production billing. Open one to see how it was built, and what it actually looks like.

01AI & data

Every database. Zero manual setup.

  • Python
  • FastAPI
  • Postgres
  • React
Database onboarding screen, discovering and validating operational database tables before they are ingested into the platform.
01AI & data

Every database. Zero manual setup.

DataNexusSchema discovery and connector validation, before a row moves.

A control plane that discovers schemas, validates connectors and provisions multi-tenant ingestion, so onboarding a new operational database is a review rather than a fortnight of manual setup.

  • Python
  • FastAPI
  • Postgres
  • React
02Data platform

Ship clean data. Automatically.

  • Python
  • Airflow
  • Postgres
  • TypeScript
Terminal from a one week spike, connecting PostgreSQL to Snowflake with schema, null and type validation applied before the pipeline is deployed.
02Data platform

Ship clean data. Automatically.

FlowStackPostgres to warehouse, with the validation in front of it.

Schema, null and type validation applied at the boundary, plan normalisation behind it, and ETL orchestration that deploys from one command instead of a runbook nobody has read since January.

  • Python
  • Airflow
  • Postgres
  • TypeScript
03Data engineering

The system that stopped needing babysitters.

  • Python
  • Airflow
  • Postgres
Production billing pipeline running on AWS Glue, with schema validation and line item reconciliation across its Bronze, Silver and Gold stages.
03Data engineering

The system that stopped needing babysitters.

Carrier billingBilling workflows used to bounce between people, spreadsheets and manual approvals.

We turned the whole thing into one automated system. Payloads land, anomalies are caught at the schema boundary, and Bronze-to-Gold billing data comes out the other side with line-item reconciliation and monitoring in front of it.

141successful workflows

Ghazanfar Sheikh, DevVaults, measured 2026-09-14. Counted by the studio from the workflow runs completed by this system, and attested rather than exported from a monitoring tool.

  • Python
  • Airflow
  • Postgres
04AI platform

Ask the platform, not the analyst.

  • Python
  • FastAPI
  • Next.js
  • TypeScript
Monitoring view of an AI analytics platform, with predictive forecasting, anomaly alerting and a natural language query panel.
04AI platform

Ask the platform, not the analyst.

Enterprise AIForecasting, anomaly alerting and query in plain language.

Predictive forecasting and anomaly detection over the warehouse, with a natural language query panel in front of both, so the question gets asked by the person who has it.

  • Python
  • FastAPI
  • Next.js
  • TypeScript
The receipts

Here's what happened after we hit deploy.

141
successful runs
SourceGhazanfar Sheikh, DevVaults, measured 2026-09-14. Counted by the studio across completed production workflow runs, and attested rather than exported from a monitoring tool.
03
iterations before launch
SourceGhazanfar Sheikh, DevVaults, measured 2026-09-14. Counted by the studio as the number of full build iterations reviewed before the system went to production.
00
rollbacks
SourceGhazanfar Sheikh, DevVaults, measured 2026-09-14. Counted by the studio as production deploys reverted since launch, and attested rather than exported from a deployment log.
99.9%
system availability
SourceGhazanfar Sheikh, DevVaults, measured 2026-09-14. Observed availability of the production system, attested by the studio. Not a monitored service level agreement and not a contractual commitment.

It shipped. It stayed shipped.

Field notes

  • 17:20
    Pull request opened
    #418 · offline queue for field reports
  • 18:05
    Review
    3 changes requested. 2 approvals. No fires.
  • 20:14
    Tests passed
    Full suite green · typecheck clean
  • 21:38
    Deployed
    Production. Nothing broke. Suspiciously smooth.
  • 23:50
    Production check
    Healthy. Metrics clean. We're going home.
SYSTEM / 03

No culture manifesto. You can watch us work instead.

Four scenes from the studio. The hardest problem goes on the table early, the architecture gets argued over and redrawn, the talking stops, and the unglamorous checks happen before you ever see a demo.

Five colleagues around a desk with two open laptops, one seated and four standing, mid discussion.

Good work gets challenged.

Not your title. Not your seniority. The idea. Working sessions exist to expose the problem while it is still cheap to be wrong about it.

Engineering × Product
Five colleagues around a table with laptops and coffee, a wall of sticky notes behind them.

Building is multiplayer.

Engineers beside designers. Designers beside product. Nobody throwing Figma files over walls.

Working session
An engineer working alone on a laptop, seated on a leather sofa against a slatted wood wall.

Then the room goes quiet.

Headphones on. Slack ignored. The debate is over and somebody has to make the thing work.

Build · Test · Repeat
An engineer in profile reading a printed document beside a bookshelf.

Details live here.

The 8 pixels nobody requested. The edge case nobody noticed. The interaction that simply feels better.

Review · Validate · Ship

We don't hire people to stay in their box. Curious people make better products. See what's open

Ideas go in. Products come out.

Still thinking about that one idea?

The one sitting in your Notes app. The one everyone says is ambitious. The one that might actually work. Send it our way.

What are you trying to build, and what happens if it works? Two sentences is plenty.

Worst case: we have a good conversation. Best case: we ship something people remember.