About Queenstownhub
Queenstownhub exists because too many good engineering teams waste their best hours fighting the platforms that are supposed to help them.
Queenstownhub builds and operates an API gateway and developer-experience platform for software product teams. In practical terms, that means we sit between your services and the consumers of those services — handling authentication, rate limiting, traffic routing, and observability — so your engineers do not have to build and maintain that infrastructure themselves. We serve teams across New Zealand and the Asia-Pacific region: primarily software product companies, SaaS businesses, and digital-native enterprises that have moved beyond prototyping and need reliable, scalable API infrastructure to support real users. Our platform is cloud-native, priced by request volume, and designed to be operational within a single business day. We do not offer bespoke professional-services engagements, on-premise installations, or custom development against client specifications. Our value is in a well-maintained shared platform, not in hourly consulting.
Queenstownhub was founded in Wellington in 2021 by a small group of engineers who had spent the previous decade building API infrastructure inside larger organisations — and repeatedly watching the same problems surface at the same scale milestones. The company is deliberately small: a micro team of six, divided between platform engineering, developer experience, and customer success. That size is a considered decision, not a temporary condition. Smaller teams ship faster, maintain clearer accountability, and hold the codebase with greater care than a team ten times the size. Since founding, we have processed more than 4.2 billion API requests across our platform and supported over 180 product teams at various stages of growth. The work has taught us that the most consequential scale problems are rarely the dramatic ones — they are the quiet accumulation of undocumented endpoints, inconsistent authentication patterns, and alert fatigue from thresholds set too loosely. Our platform addresses those problems structurally rather than leaving them to individual discipline. We operate from a teal-modern aesthetic in everything we build: clean information hierarchy, deliberate use of colour to signal state, and interfaces that surface only what is necessary at each moment. That same clarity shapes how we communicate — in our documentation, our support responses, and this page. We are honest about what the platform does not do: it is not a service mesh, it does not replace an internal developer portal for large enterprises, and it does not provide AI-generated API specifications. Where a team's requirements fall outside what Queenstownhub covers well, we say so directly rather than over-promising.
We ship fewer features than our roadmap could support because each feature we ship must be understandable without a support ticket. A platform with 40 half-explained capabilities is less useful than one with 15 that work exactly as documented.
Every capability is independently accessible via API. Teams that want only the gateway, only the documentation engine, or only the alerting module can use exactly that — and add the rest later when the need is real, not anticipated.
API performance depends on upstream service latency, client network conditions, and request payload size — factors outside Queenstownhub's control. We publish P95 and P99 benchmarks from our own infrastructure and never attribute external slowdowns to our own optimisations.
For technical questions, partnership enquiries, or to discuss whether the platform fits your requirements.
Level 4, 22 Willeston Street, Wellington 6011, New Zealand