Massage Service Hub
An operating platform for massage businesses and their customers
An Ezion-owned product connecting massage business discovery and booking with the operational tools used to run the service.
Visit productEzion / Selected work
Selected work
Owned products and delivery work, described without invented outcomes.
Owned products
Selected work
Owned products and delivery work, described without invented outcomes.
Two audiences, one source of truth
A visitor browses Sydney shops and therapists by suburb and by service type, opens a shop profile, and compares services, prices, therapists and booking options. A participating business edits the same records from its own administration surface. Because both sides read the same data, a change made by the business is the change a customer sees, and the platform does not need a reconciliation step between a public listing and an operational one.
Discovery that stays honest
Shops are browsable by suburb, by service category and on a map, and profiles carry a completeness indicator so a partially filled listing is visible as such rather than presented as finished. Featured placements are labelled as paid priority listings wherever they appear, so a visitor can tell promotion from ranking. Those are product decisions, not styling: they determine what the directory is allowed to imply.
Built to keep running while it changes
The public site, the business administration interface and the shared backend are deployed as separate services behind a single reverse proxy, with health checks in the release path and centralised logs. The product is continuing work rather than a finished portfolio piece, so each change is judged against a system that has to stay usable while it is modified.
Ezion Guide
A bilingual publication with its own editorial rules
Ezion Guide is our English and Korean publication for practical Australian household technology, energy and home network guides.
Visit productEvery guide is published twice, deliberately
Each English guide has a Korean counterpart, and the two are linked as translations of one another rather than published as unrelated pages. That mapping drives the language switch, the hreflang annotations and sitemap membership, so a reader and a search engine reach the same article in the language they asked for instead of a near-duplicate.
Sources and review dates carried in the article
Guides state who wrote them, when they were last reviewed, and which primary sources support figures such as energy ratings, tariffs or running costs. Where a number depends on a plan, a state or a model, the guide says so instead of presenting one figure as universal. Advertising and affiliate relationships are disclosed on a dedicated page, and a commercial relationship does not decide an article's conclusion.
Operated like a product, not a blog install
Consent is handled by a certified consent platform with reject-first defaults, `ads.txt` is served from a version-controlled file mounted read-only over the document root so publishing cannot overwrite it, and the tag configuration lives in a must-use plugin rather than in theme settings a later update can drop.
The problem the product addresses
Massage Service Hub brings public business discovery and booking together with the tools a participating business uses to manage its service. The public experience and the operating experience are treated as one system: availability, business information and booking decisions need to remain consistent across both.
What Ezion is responsible for
Ezion designs, develops and operates the product. That includes the public directory and booking journeys, business administration interfaces, shared backend services, deployment automation and operational monitoring. The product is continuing work rather than a finished portfolio mock-up, so decisions are tested against a system that must remain usable while it changes.
What this demonstrates
The work demonstrates product planning across customer and operator needs, responsive web delivery, API and data integration, release discipline and day-to-day operational ownership. We describe the system itself rather than publishing unsupported customer outcomes. Public product pages are linked so visitors can inspect the live service directly.
Evidence before claims.
We publish work we can verify and do not use unsupported metrics, testimonials or client outcomes.
Bring us the complicated part.
A useful first conversation is enough to define the problem and the next decision.
Start a conversation