Skip to content
Built in NZ · For ANZ operations

ERP, but only the parts you actually use.

Most ERPs ship as one giant suite — you pay for everything and only use a slice.OpsUI splits the same scope into 21 modules. Buy what you need today, add the rest when you need them, and never pay for a "Manufacturing" tab you'll never open.

Modular ERP, WMS & CRM for ANZ operations. Buy what you use. Pay what you owe. Supported in time zone.

TL;DR

OpsUI is a modular ERP, WMS & CRM for ANZ operations, founded in January 2026 in Wainui, New Zealand and Melbourne, Australia. The product is bootstrapped, self-funded, and built by a four-person team. Customers buy from 21 individually-priced modules instead of a single suite, with pricing public on the page, NZ data hosted in NZ and AU data hosted in AU, and support delivered in time zone.

How it started

OpsUI was founded in January 2026, with regional domains live across both New Zealand and Australia from day one. The pitch was simple: ANZ operations leaders kept telling us they were paying for whole ERP suites and only using a slice. So we split the same scope into 21 modules, put the prices on the page, and launched into both markets the same week.

Same product on opsui.co.nz and opsui.au, same release cadence — just routed to the right datacentre and supported by people on the right time zone. Wainui (north of Auckland) is HQ for engineering and customer success; Melbourne is HQ for the Australian arm.

We are bootstrapped and self-funded — no investors, no quarterly board pressure to ship features that look good in a deck. The roadmap is shaped by the operators we onboard, and the disciplines on /careers are where we tend to grow when growth is justified.

Jan 2026
Founded
20
Modules shipped
NZ · AU
Regions live
Bootstrapped
Funding

How we think about the product

Modular by default

Every feature lives in a module you can switch on or off. Pricing is per module, so the bill matches the scope. The Enterprise tier is custom-quoted because most teams don't need it.

ANZ-first, not ANZ-after

GST, RD addresses, NZ Couriers, AU/NZ business hours support. Built into the workflows, not bolted on later. Production data for each region stays in-region.

Honest scope

If we don't integrate with your carrier, we say so on the integrations page. If a feature is on the roadmap, it doesn't live in marketing copy yet. You'll know what you're buying before you sign.

Who's behind it
Joshua Steenkamp, Quality Assurance Specialist at OpsUI
Joshua Steenkamp
Quality Assurance Specialist

Keeps the modules honest. Every release — module updates, integration changes, UI patches — ships through Josh before it reaches customers. The reason an OpsUI release feels boring is because Josh has already done the worrying.

Moussa Mansour, Full Stack Developer at OpsUI
Moussa Mansour
Full Stack Developer

Works across the front and back end of OpsUI — turning product ideas into polished features while balancing performance, usability, and maintainable code. Contributes to design, architecture, and UX decisions.

Addison Ly, Full Stack Developer at OpsUI
Addison Ly
Full Stack Developer

Shipping real product work across the stack — React, TypeScript, the Node API — while finishing his studies. Joins design reviews, owns small features end-to-end, and ships code that real customers use.

Design partner programme

Currently onboarding design partners.

OpsUI launched in January 2026 and is in its first cohort of design partners across NZ logistics and AU light manufacturing. Design partners get pricing locked in for the first 12 months, direct access to the founders for product decisions, and visible influence on the roadmap published at /changelog.

We will publish named customer stories when partners are ready for them — not before. If you would rather wait until OpsUI has a public logo wall, that is fine. If you would rather be in the cohort whose feedback shapes the next 12 modules, the conversation starts on the demo call.

Two regions, one product

OpsUI runs on two regional domains: opsui.co.nz for New Zealand and opsui.au for Australia. Production data for each region is hosted in-region — NZ data stays in NZ, AU data stays in AU. The login app you use is the one for your region.

Same product, same modules, same release cadence. Just routed to the right datacentre and supported by people on the right time zone.

Common questions

Things people ask before signing.

When was OpsUI founded?
OpsUI was founded in January 2026, in both New Zealand and Australia simultaneously. opsui.co.nz and opsui.au launched the same week, with engineering and customer success based in Wainui (north of Auckland) and the Australian arm based in Melbourne.
Are you VC-backed or bootstrapped?
Bootstrapped and self-funded by the founders. We answer to customers, not investors — which is part of why pricing is on the page and the roadmap is honest about what is shipped versus what is planned.
Where is OpsUI data hosted?
NZ production data stays in NZ and AU production data stays in AU. Each region runs on its own domain (opsui.co.nz / opsui.au) with its own database. We do not replicate customer data across the Tasman.
What is the tech stack?
TypeScript end to end. React on the front, Node on the API, Postgres for primary storage. The marketing site is Vite + Tailwind. We pick boring, well-supported tools so the team can spend its energy on the modules.
Are you hiring?
Not on a rolling job board. If you are great at engineering, customer success, or GTM and the disciplines on /careers sound like you, send a CV to [email protected] and we will be in touch when there is a real conversation to have.

Last updated

Registered office

OpsUI Limited

71 Parish Drive
Wainui, Auckland, 0932
New Zealand
Talk to a human

Pick the right inbox.

See the modules. Pick the ones you need.