What a council needs to ask before buying
Hosting, backups, recovery, insurance, escrow, support and what we record about the people who use it. Every figure below is read from the same register that governs what may be written on a quote, so a commitment that is not in place prints here as not in place rather than being left out.
No council uses PaveKeep yet. Everything below is a commitment rather than a track record, and the difference is stated wherever it matters.
Who you would be contracting with
| Entity | Morid Pty Ltd trading as PaveKeep |
| ABN | 21 667 242 631 |
| Contact | Mahdi Davoodian, Chief Executive Officer |
| sales@pavekeep.com.au | |
| Based | Canberra region, NSW |
These are read from the same file that fills them into every document a council receives, so the ABN on a quote and the ABN on this page cannot disagree.
Where the data lives
A council’s environment runs in Australia, in AWS Asia Pacific (Sydney). It is stood up when a council asks for one rather than kept running in advance, and provisioning in the Australian region precedes any load of council data. Our own development and staging systems run in the EU and hold none of it — stated plainly, because an IT reviewer who discovers an undisclosed offshore dependency later will not care that it held nothing. The same deployment procedure installs PaveKeep on a council’s own infrastructure where policy requires that.
| Region | AWS Asia Pacific (Sydney), ap-southeast-2 |
| Our development systems | Hetzner, EU |
| Provisioning | Stood up per council on request — not kept running in advance |
| Lead time, from a signed order | 3 working days |
Backups
Nightly automated backups of the whole platform, kept 35 days — long enough that a month-end is still recoverable a few days into the next month, which is when a finance team discovers it needs one. They protect against infrastructure loss and they are NOT a way to undo something a council did: restoring one would roll every council back together. Undoing your own work is the next section, and the answer there is better.
| What they cover | Platform-wide, for infrastructure loss — not a per-council restore |
| How often | Nightly, automated |
| Kept for | 35 days |
| Restore tested | quarterly |
No restore drill has been recorded since 2026-10-03. The procedure exists and is run quarterly; it has not been run yet, and that is a different sentence from "no failures".
Undoing something that went in wrong
Most of what goes wrong is undone by the council, in seconds, without asking us. An import is one transaction, so a half-written network cannot exist; a filed survey is retracted and stays on the record with who filed it and who voided it; a corrected network file updates the roads it can identify rather than duplicating them. Above those, a whole-council restore point can be taken before something risky and put back by us, touching no other council.
| A part-finished import | An import is one transaction — a partial network cannot be left behind |
| A survey filed in error | A council retracts a filed survey itself, however it was filed; the run stays on record with who filed and who voided it |
| A corrected road file | A corrected network file updates the roads it can identify by the council's own asset id, rather than duplicating them |
| Removing a network | A network with nothing recorded against it can be removed by the council |
| An import retracted after work was recorded | A wrong network import can be retracted after work has been recorded against it; the roads leave the network and nothing is deleted |
| A restore point you take yourself | A council's whole data can be captured as a restore point and put back, without touching any other council |
Not in place: Rolling one council back to a MOMENT — 2:55pm yesterday — rather than to a restore point. A council can take a restore point before something risky and have it put back, and every destructive operation can be undone on its own; what is not available is a continuous clock to choose any second from.
Getting your data out
A council’s own data, exported to them weekly, in formats they can open without us. The whole network also exports in a standard mapping format at any time, into the council’s own GIS. Nothing is held hostage by the subscription.
| Your data, exported to you | weekly |
Insurance
Public liability is held and current. Professional indemnity is a different cover for a different risk and we do not hold evidence of it, so we do not claim it — see the line below. A certificate of currency naming the policy and the period is available on request; the policy number is not published here.
| Public liability | $20,000,000 |
| Policy | General and products liability, $20,000,000 — NRMA Business Insurance policy BP 6313028 / INT, to 19 January 2027 |
| Current until | 19 January 2027 |
Not in place: Professional indemnity cover. Public liability is held and evidenced at $20,000,000; professional indemnity is a different cover for a different risk and the certificate on file does not show it, so it is not claimed. $5,000,000 is the level Australian councils commonly ask for, and it is a target rather than cover.
If we stop existing
The source is deposited with the company’s solicitor under a deed with defined release triggers, so a council is not depending on the company continuing to exist. Formal third-party escrow is available where a council requires it and meets the difference in cost.
| Source deposited with | Morid Pty Ltd's solicitor, under a deed of deposit |
| Deposited | at each production release and at least every six months |
Support
Councils work business days, so that is what is covered: out-of-hours cover buys nothing and would be the first commitment to break. Response is not resolution — what is promised is that a person replies and starts work, not that the problem is fixed by then.
| Hours | 9:00–17:00 AEST/AEDT, Monday to Friday, excluding national and NSW public holidays |
| First reply, outage | within 4 business hours |
| First reply, anything else | within 2 business days |
| Notice of planned maintenance (business days) | 5 |
What we record about your people
PaveKeep records no information about the people who use it or are shown it. Not “we anonymise it” and not “we do not sell it” — nothing is stored, nothing is transmitted, no third-party service is involved, and no council tenant is observed. The one instrument that exists measures a demonstration session on the presenter’s own machine for the length of that session.
| The one instrument that exists | Presenter-side, session-local, four events |
Anything here that matters to your procurement team and is not answered, ask for — the answer is either in the register behind this page or it is an open question, and we will say which.