Get in touch

One address. A person reads it.

No ticketing system, no auto-responder, no form that goes nowhere.

Email Shard Labs

If you are asking for access

It helps to know a little. None of it is required, and there is no wrong way to write it.

Which productShard Audit, Shard Books, or both — they are separate betas.
What you doFor Shard Audit: your role and what you are assessed against — auditor, quality or compliance manager, consultant, scheme owner. For Shard Books: what your business does, or what you are trying to start.
Why nowWhat made you look. A certification coming up, a spreadsheet that has stopped coping, a first BAS, or simple curiosity — all useful.
What could be done betterThe part of the job you dread, or the thing your current tool makes harder than it needs to be. That is usually what we should show you first.
How you workIf there is anything that would make this easier for you — plain email over calls, written over spoken, more time to reply — say so and we will work that way.

Early access is free. In return we ask for honest findings, including the unflattering ones.

Elsewhere

We post occasionally, mostly about what we are building and what we got wrong.

LinkedInShard Labs Pty Ltd
EmailThe button above. One address, read by a person.

Where we are

Shard Labs is based in Brisbane, Queensland, and works across Australia and New Zealand.

This website is served by Cloudflare’s global edge network. We have enabled no analytics and no logging, so we receive nothing about your visit — that is measured and published, not asserted.

The products are a different question, and a more important one. Where we host Shard Audit, it runs in AWS Sydney (ap‑southeast‑2), in an Australian account. Shard Books is built to be self‑hosted — including the model that reads your receipts — so its records never have to leave the machine they are on.

As we grow into other markets we will meet each region’s data-residency rules on their own terms, rather than routing everyone through one country. And because both products can run on infrastructure you control, the strongest answer to “where does our data live” stays available: wherever you decide.

Drawn, not embedded. A map from Google or OpenStreetMap would mean a request to their servers and a cookie on your machine every time this page loaded — see what this site collects.