Platform Development · Wellington
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 Wellington teams who would rather ship than re-platform in a year.
Trusted by teams across Australia, North America and beyond
Sound familiar?
Wellington is the seat of government and a tech and film hub — public-sector procurement and data sovereignty drive the platform conversation.
Wellington platform work is shaped by the public sector: NZ data residency, the NZ Privacy Act and government procurement, alongside a tech and film scene with media data at scale.
We build sovereign, NZ-resident data platforms with the controls and documentation procurement expects, and replace per-seat BI with self-hosted Superset.
Wellington is the seat of government and a tech and film hub — public-sector procurement and data sovereignty drive the AI conversation.
1"Our backend was built to reach launch. Now it slows every release down."
2"We are moving to enterprise customers and our architecture was never designed for it."
3"Our data sits in five systems and nobody trusts the numbers on the dashboard."
4"We pay per seat for Tableau, Power BI or Looker and the bill grows faster than revenue."
5"We have outages we cannot explain and no real observability to find out why."
What we do
Every engagement starts with a 30-minute call. If we cannot tell you something useful in that window, we do not take the work on.
APIs, services and data models designed for where you are going, so new features do not add fragility.
Pipelines, warehouse and a semantic layer, so the dashboard, the product and finance agree on the numbers.
Apache Superset and ClickHouse inside your product in place of per-seat BI. A stack we run ourselves.
AWS, Google Cloud or Azure done properly: infrastructure as code, CI/CD, secrets and cost guardrails.
Tenant isolation, row-level security and per-tenant configuration, so you can sell to enterprise without a rebuild.
SLOs, tracing, logging and alerting that tell you what broke and why, before the customer does.
Outcomes
We measure ourselves on what your team does differently afterwards, not on hours billed.
Typical BI licensing reduction when per-seat tools give way to embedded Superset and ClickHouse.
Tenant isolation and row-level security that let you sell to enterprise without a rebuild.
CI/CD, infrastructure as code and observability, so releases are routine and outages explainable.
Everything lands in your repo and your cloud account. No black box, no lock-in to us.
How we engage
A two-week diagnostic of architecture, data and reliability: what to fix first, what to retire, what breaks at the next scale step.
from NZ$10K
Get a proposalSix to twelve weeks: re-platform, data platform, embedded analytics or multi-tenant migration, in your repo and cloud.
from NZ$50K
Get a proposalA platform squad that builds alongside your engineers and hands the keys back. Two to four days a week.
from NZ$12K/mo
Get a proposalCompliance and data
We design for the NZ Privacy Act 2020, and for the Algorithm Charter and NZISM in public sector work.
We are headquartered in Sydney and work trans-Tasman with Wellington teams, remote-first in NZ time, with on-site visits for kickoff and key milestones when needed.
Also in Wellington
Questions
Straight answers to what Wellington teams ask before they book.
We are headquartered in Sydney and work trans-Tasman with Wellington teams, remote-first in NZ time, with on-site visits for kickoff and key milestones when needed. We work with teams across the CBD and Te Aro.
A two-week Platform Assessment can start the Monday after the scoping call. Larger engagements usually begin one to two weeks out.
Yes. We contract and price in NZD. We design for the NZ Privacy Act 2020, and for the Algorithm Charter and NZISM in public sector work.
Yes. We meet the codebase, cloud and tools you already run, and only recommend a change when staying clearly costs more than moving.
Yes. We run Apache Superset and ClickHouse embedded inside our own products, so it is an architecture we operate, not just recommend.
Yes — NZ cloud regions, Privacy Act-aligned controls, and the architecture documentation and evidence procurement looks for.
Yes — self-hosted Superset scales with infrastructure rather than per user, a real saving across an agency.
Both, and we never advise without being willing to build. If the answer is Apache Superset, we stand it up. If it is a senior hire, we write the spec and sit on the panel.
Start a conversation
Tell us what you are weighing up. We reply within one business day, in Wellington time.
We reply within one business day.