Build it properly, then keep it running.

MindStack designs and builds websites and applications for businesses, and operates the cloud infrastructure underneath them. One team from first scope to on-call.

Talk to sales See the work

Examples of the work: scoping architecture, provisioning environments, running the test suite, deploying to production, watching the dashboards

mindstack · releaselive

buildcompile · bundle
test412 specs
shipblue / green
observeon call

SuvaSydneySingapore

gridEvery build starts as a measure and a grid.layoutStructure before pixels. Blocks find their places.contentReal type, real content, one accent that converts.liveThen we keep it up, in three regions, on call.

Selected work

Constraint, decision, outcome.

All work →

Paradise Group

Energy and electrical services

Constraint: A multi-company Pacific group had its products, services, careers and country operations spread across separate sites, each with its own brand and its own login.
Decision: Consolidated everything into one platform under a single brand, so a customer in any country reaches the same company.

WordPressElementorContact Form 7

Visit the site ↗

All About Her

Retail, beauty and wellness

Constraint: A curated beauty and lifestyle range needed to sell into nine currencies, with collections, cart, accounts and a newsletter.
Decision: Built as a custom storefront rather than a themed template, so the currency and collection logic is ours to change instead of a plugin we wait on.

Next.jsVercelMulti-currency

Visit the site ↗

QR

Cloud platform

Constraint: A platform that had to stay up under load, with live events, an admin surface, and a deployment story someone other than the original author could run.
Decision: Front Door with WAF and CDN ahead of a Next.js SSR site and admin SPA, a nine-module NestJS API behind a JWT guard, Socket.io for live events, and Postgres, Redis and Blob Storage underneath. Shipped by GitHub Actions through Container Registry, secrets in Key Vault, telemetry into Application Insights.

AzureNestJSTerraform-ready

Read the case →

What we do

Three services that hand off to each other, not to someone else.

Hands over to

Web platforms

Marketing sites, customer portals and internal tools that are fast, measurable and handed over documented.

Discovery, design, build
CMS and integrations
Performance budgets

Hands over to

Product & app engineering

Web and mobile applications built to be extended by your own team, with the tests and CI to make that safe.

Product design
Web and mobile builds
Legacy modernisation

Stays with us

Cloud & infrastructure

The part most agencies leave behind: provisioning, pipelines, monitoring and someone answerable when it pages.

Infrastructure as code
CI/CD and observability
Managed operation

How we build

One pipeline, running continuously.

01Scope
Paid discovery
Ends in an architecture, a plan and a number. Yours to take elsewhere.
02Build
Two-week increments
In your repository, in your cloud account, reviewable from day one.
03Ship
Staged release
Rollback ready, monitoring wired before launch, runbook written by the builders.
04Run
On call
We operate it, or train your team to. Handover is a date, not a hope.

Placeholder process — replace with your real environments and on-call arrangement

Engagement

Three ways to work with us, ranges published.

How pricing works →

Comparison of MindStack engagement models: Project, Embedded team, Managed infrastructure.
Attribute	ProjectRange TBC	Embedded teamRange TBC	Managed infrastructureRange TBC
Billed	Fixed scope	Per month	Per month
Best when	A launch with a date attached	Continuous delivery alongside your own engineers	Someone accountable for uptime
Who you get	One delivery team	Named lead, standing roadmap	On-call rotation
How it ends	On handover, with the code and accounts yours	Any month, on notice	Any month, on notice. Available on its own

Straight answers

The questions that decide it.

Answered here rather than on an FAQ page, because these are the objections that stop a project starting.

Who owns the code and the cloud account?: You do, from the first commit. Placeholder — confirm your actual arrangement.
What happens after launch?: Either we operate it under a managed agreement, or we hand over against a documented plan on an agreed date.
How quickly can you start?: Placeholder — your real lead time. Vague answers here cost deals.
What don't you take on?: Placeholder — naming what you decline is the most credible thing on this page.

Who you'll work with