Gold Coast, Queensland
The three backend pieces a small game team actually needs.
Save sync, leaderboards, remote config. Not a platform, not an engine, not an analytics suite you have to adopt whole. Three services, each priced and scoped on its own, run for studios that would rather not operate a backend.
Catalogue
Three services, and what each one commits to.
Every row states what is included, what the target is, and what the contract basis would be. Two of the three are not open yet, and the table says which.
| Service | What is included | Target | Contract basis | Status |
|---|---|---|---|---|
| Save sync | Per-player save blob, conflict resolution on last-write with a client-supplied vector, restore on a new device, export on request | Write acknowledged in under 400 ms at the 95th percentile from an Australian client | Monthly, per monthly active player, no minimum term | In development |
| Leaderboards | Global and window-scoped boards, server-side score validation hooks, per-board reset schedules, abuse flags exposed to you rather than acted on for you | Read in under 200 ms at the 95th percentile from an Australian client | Monthly, per board, no minimum term | In development |
| Remote config | Typed key and value store, staged rollout by cohort, instant rollback, full change history with who changed what | Config fetch in under 150 ms at the 95th percentile, cached client side with a stale-while-revalidate window you set | Monthly, flat, no per-seat charge | Not started |
Nothing is live. No service in this table is accepting customers, the targets are design targets rather than measured results, and no service level agreement is on offer. When one opens, this table changes and the status column is where you will see it.
The shape of it
Three services, not a platform.
The distinction matters more than it sounds, and it is the reason this company exists rather than a recommendation to use one of the large suites.
What a platform costs you
Adopt a backend suite and you get save sync, but you also get its analytics, its identity model, its notification system and its opinion about how your player accounts work. Six months later, moving one piece means moving all of them, and the export is a JSON dump nobody has tested restoring.
What we are doing instead
- Each service is separately contracted and separately priced. Take one, take three, cancel one.
- No shared identity model. You give us an opaque player identifier that means something to you and nothing to us.
- No analytics of any kind. We do not want your gameplay telemetry and we have nowhere to put it.
- Export is a documented, tested, self-service operation, not a support ticket. The test that it restores runs on the same schedule as the backup.
What that means legally
For every service in the catalogue we act as a processor: we hold your players' data on your instructions and we do not decide what it is for. You remain the entity your players deal with, and you remain responsible for telling them what you collect. The privacy policy splits along that line rather than blurring it, which is unusual enough to be worth pointing at.
Position
Where the data would sit, and why that is a decision.
Primary storage would be in an Australian region. Not because Australian law requires it, which it mostly does not, but because a studio in Australia serving Australian players should be able to answer "where is it" with one country rather than a paragraph.
Australian Privacy Principle 8 and section 16C of the Privacy Act make an Australian business accountable for what an overseas recipient does with personal information it disclosed. Keeping the primary copy onshore removes that question for the largest part of the data rather than managing it. Where a component genuinely has to sit elsewhere, the privacy policy names the country in a table rather than describing it as a global network.
This is a commitment about a service that does not exist yet. It is here because the architecture decision is being made now, and the moment to write it down is before it is expensive to keep.
Company
The registrable facts.
On an Australian public register, checkable without asking us.
- Legal name
- CLOUDRIDGE TECHNOLOGIES PTY LTD
- Entity type
- Australian proprietary company, limited by shares
- ACN
- 696 705 478
- ABN
- 69 696 705 478
- ABN status
- Active from 30 March 2026
- GST
- Not currently registered for GST
- State
- Queensland
- Verify
- abr.business.gov.au, free and without an account
- Contact
- [email protected]
CLOUDRIDGE TECHNOLOGIES PTY LTD holds no ISO/IEC 27001 certification, no SOC 2 Type I or Type II report, no IRAP assessment and no other independent security accreditation, and will not represent otherwise until one is genuinely held. It has no customers, no published uptime record, no case studies and no outside investment. For infrastructure that is a serious gap and we would rather you weighed it than discovered it.