Platform Development · San Francisco
San Francisco's platform engineering partner — the backend, data and infra your product scales on.
We design and build the platform underneath the product: APIs, data, cloud and the reliability work that decides whether you scale or stall. Built for San Francisco teams who'd rather ship than re-platform in a year.
Get a response within 1 business day
Why San Francisco teams call us
The work you can't afford to get wrong.
San Francisco is the global tech and AI epicentre — the bar isn't whether you can build, it's whether you can ship something defensible and scalable faster than a well-funded startup.
Our backend was built to get to launch and it's now the thing slowing every release down.
We're going multi-tenant / enterprise and our architecture wasn't designed for it.
Our data is spread across five systems and nobody trusts the numbers in the dashboard.
We're paying per-seat for Tableau / Power BI / Looker and the bill scales worse than our revenue.
We have outages we can't explain and no real observability to find out why.
What we do
What platform engineering actually covers.
Every engagement starts with a 30-minute call. If we can't tell you something useful in that window, we don't take it on.
Platform & backend architecture
APIs, services and data models designed for where you're going, not where you launched — the structure that lets you add features without adding fragility.
Data platform
One source of truth: pipelines, warehouse/lakehouse and a semantic layer, so the dashboard, the product and finance all agree on the numbers.
Embedded analytics & BI
Replace per-seat Tableau / Power BI / Looker with Apache Superset and ClickHouse, embedded inside your product — the reference architecture we run for our own platforms.
Cloud & DevOps
AWS, GCP or Azure done properly: IaC, CI/CD, environments, secrets and cost guardrails — so deploys are boring and the bill is predictable.
Multi-tenant SaaS
Tenant isolation, row-level security, per-tenant config and the data architecture that lets you sell to enterprise without re-platforming.
Reliability & observability
SLOs, tracing, logging and alerting that tell you what broke and why — before the customer does. Performance and caching that hold up under load.
Why San Francisco
In your timezone. Onsite when it counts.
Bay Area platforms are judged by technically sophisticated buyers and investors: multi-tenant SaaS that scales cleanly, data infrastructure that holds, and AI features carrying the evals, observability and cost controls a Series A/B technical diligence will probe.
We build the platform and data layer underneath fast-moving products — the unglamorous architecture that turns a demo into something that scales and survives diligence — and run ClickHouse + Superset ourselves.
What "good" looks like.
We measure ourselves on what your team is doing differently — not on hours billed.
Typical BI licensing reduction when we replace per-seat Tableau / Power BI / Looker with embedded Superset + ClickHouse.
Architecture that lets you sell to enterprise — tenant isolation and row-level security — without a rebuild.
CI/CD, IaC and observability so releases are routine and outages are explainable, not mysteries.
Everything lands in your repo and your cloud account. No black box, no lock-in to us.
How we engage
Three ways to start. All begin with a call.
Engagement
Platform Audit
2-week diagnostic of your architecture, data and reliability — what to fix first, what to retire, what'll break at the next scale step. Fixed scope, fixed fee.
from US$10K
Engagement
Platform Build
6–12 week engagement: re-platform, data platform, embedded analytics or multi-tenant migration, delivered in your repo and infrastructure.
from US$50K
Engagement
Embedded platform team
An embedded platform squad that builds alongside your engineers and hands the keys back. 2–4 days a week, quarterly outcomes.
from US$12K/mo
FAQ
Direct answers to what San Francisco teams ask before they book.
Are you based in San Francisco?
We're an Australian-headquartered firm and work with San Francisco teams remote-first in your timezone, with onsite visits for kickoff and key milestones. We work with teams across SoMa, the Financial District and the wider Bay Area.
How fast can you start?
A 2-week Platform Audit can start the Monday after the scoping call. Larger engagements typically begin 1–2 weeks out, depending on team availability.
Do you work in USD and to US compliance?
Yes — we contract and price in USD. We design for SOC 2, HIPAA where health data is in scope, the NIST AI Risk Management Framework, and state privacy law (CCPA/CPRA). We're an official Vanta partner for the evidence side.
Do you work in our existing stack or impose your own?
Your stack. We meet the codebase, cloud and tools you already run, and we only recommend a change when the cost of staying is clearly higher than the cost of moving.
Can you help with the embedded analytics / Superset piece specifically?
Yes — it's a core competency. We run Apache Superset and ClickHouse embedded inside our own venture-studio products, so the reference architecture is one we operate, not just recommend.
We're raising — will our architecture survive technical diligence?
Yes — we harden scalability, multi-tenancy, security and run-cost so the technical diligence is a tick, not a flag, and we'll sit in the room for the technical session.
Can you scale our multi-tenant SaaS?
Yes — tenant isolation, row-level security and the data architecture to grow from startup into enterprise without re-platforming.
Do you actually build, or just advise?
Both — and we never advise without being willing to build. If we tell you the answer is Apache Superset, we'll stand it up. If we say hire a senior engineer, we'll write the spec and sit on the panel.
Related
Stop benchmarking. Book a call.
Thirty minutes. No deck. We'll either tell you what to do next, or who you should be talking to instead of us.
Book a 30-min call