Application — Cloud Run
A managed, auto-scaling service with no exposed server to log into and attack. New versions deploy without taking the booking page down.
The technology behind AURI
Fast, lightweight, and secure — by design, not by add-on.
AURI is a deliberately lean, server-rendered system on your own dedicated Google Cloud infrastructure. Most booking software is the opposite — a heavy app on a shared database, patched for security after the fact.
Same-week slot no commitment forward this to your IT team
In one line
AURI is a server-rendered web application — Go, Templ, HTMX, PostgreSQL — deployed as a dedicated single-tenant instance per client on Google Cloud, with TLS 1.2+ in transit, AES-256 at rest, and daily backups with point-in-time recovery.
The philosophy
Less software, fewer moving parts, fewer ways to fail.
When a guest opens your booking page, their phone downloads no heavy JavaScript app to assemble the screen. AURI renders every page on the server and sends finished HTML — the browser's only job is to show it.
With no front-end framework pulling in hundreds of third-party packages, the most common route for supply-chain attacks isn't there. The dependency list is short, chosen on purpose, and ours to answer for. The simplest system that does the job is also the fastest and the safest one.
What it's built from
- Go Google's language for fast, reliable services.
- PostgreSQL The database trusted by banks and public institutions.
- Templ Pages built on the server — fast, and a whole class of attacks cut off.
- HTMX A tiny, stable library instead of a heavy framework.
Automated test and security checks run on every change before it ships.
The foundation
Your spa runs on Google's infrastructure, not a server in someone's office.
Your spa inherits Google's data-centre physical security, round-the-clock monitoring, and compliance certifications. AURI runs entirely on Google Cloud Platform and operates no physical servers of its own. ISO 27001, SOC 2, and PCI DSS are Google's, and everything on their platform sits behind them.
Database — Cloud SQL
Google-managed PostgreSQL, with patching, backups, and failover handled by the platform — not by hope.
Secrets — Secret Manager
Passwords, API keys, and encryption keys live in Google's secret store — never in the code, never in a config file on a disk.
The region is yours to choose: europe-west in the EU by default, or Doha (me-central1) and Dammam (me-central2) for Gulf properties that want in-region residency.
The strongest part of the architecture
Your data never sits in the same database as anyone else's.
Every client gets a genuinely dedicated environment: their own database, their own application instance, their own domain and branding. AURI is not a shared platform holding everyone's data in one big database separated by a column.
The most common way customer data leaks in shared software is a filtering mistake in a multi-tenant database. It cannot happen here. There is nothing to filter — only your data, in your database.
Want the isolation model walked through end to end?
- A dedicated PostgreSQL databaseper client.
- A dedicated application instance— yours alone.
- Isolation by architecture— not by access control.
The controls
The security specifics, in one table.
Nothing exotic — the disciplined basics, running on every request.
| Control | What runs today |
|---|---|
| In transit | TLS 1.2 or newer on every connection — nothing travels in plain text. |
| At rest | AES-256 on every disk and every backup — the Google Cloud default. |
| VIP records | Email and phone additionally encrypted in the application with AES-256-GCM — a database dump shows ciphertext, not contact details. |
| Passwords | bcrypt hashes only — no one, including us, can read the original. |
| Sessions | 32-byte random tokens in HttpOnly, Secure cookies, expiring after 30 days — no immortal logins. |
| Rate limits | Per-IP caps — sign-in 5 a minute, booking 10 — so brute force hits a wall. |
| Timeouts | Every request runs under a hard timeout, with a cap on request size — a stuck or oversized request cannot hold the system. |
| Audit log | Append-only record of who viewed, edited, exported, deleted, or anonymized a guest record — when, and from which IP. No user can edit or erase it. |
The worst case, planned for
Built for the day something goes wrong, and the day you want to leave.
The honest promise isn't "nothing will ever fail" — it's that your data is recoverable, and never trapped.
If something goes wrong
- Automated daily backupsplus point-in-time recovery — restore to the minute before a mistake, not just to last night.
- Documented recovery targets— an hour to restore service (RTO), five minutes of data at most (RPO).
- High availability in production— a regional Cloud SQL configuration that fails over if a zone goes down, with deletion protection on.
- Zero-downtime deployments— new versions roll out on Cloud Run without taking the booking page offline.
If you want to leave
- You own the data.You are the data controller; AURI is the data processor acting on your instructions.
- One-step export, any time— structured JSON, the machine-readable format GDPR Article 20 calls for, plus CSV for everyday lists. No ticket, no extraction fee.
- A GDPR toolkit, not a checkbox— consent capture with withdrawal, anonymization, and automatic anonymization once the retention window lapses (24 months by default, configurable).
For your IT team
A documented REST API, not a black box.
Your data stays reachable by the systems you already run.
REST API v1
11 endpoints covering services, availability, bookings, reports, and metrics.
Bearer authentication
Per-key tokens, rate-limited at 100 requests a minute per key.
OpenAPI documented
A machine-readable spec with an interactive reference — your developers read it without us in the room.
Beyond the API, custom work is scoped as part of an implementation — possible because every client runs a dedicated instance. See how AURI connects to your PMS.
The honest boundaries
The limits, stated plainly.
Here is where the lines are today. A page that only boasts is a page to distrust.
No external security audit — and we don't claim one
We run our own automated test and security checks on every change before it ships. That is the basis for "extensively tested" — not a certificate we don't hold.
We publish no performance numbers
"Fast" and "lightweight" are engineering choices we describe honestly. A speed figure depends on your hardware and booking mix, so we won't quote one we can't stand behind. We validate speed against your real load on the call.
The audit log is scoped to guest records
It covers actions on guest records — not every screen in the system. We say so rather than implying surveillance the system doesn't perform.
Certifications belong to Google
ISO 27001, SOC 2, and PCI DSS certify the Google Cloud infrastructure AURI runs on. They are Google's, inherited by what runs on the platform, never an AURI-held certificate. Everything else on this page is a control that exists in the system today.
A vendor who tells you where the line is, is a vendor you can trust about what sits inside it.
FAQ
For you, and your IT person.
Is each client's data separated from other clients?
Yes — completely, and by architecture rather than by policy. Another client's data cannot leak into yours, because it is not in your database to begin with.
Where is AURI hosted?
Entirely on Google Cloud Platform — Cloud Run for the application, Cloud SQL for the PostgreSQL database. The region is chosen with you: europe-west in the EU by default, or Doha (me-central1) and Dammam (me-central2) for Gulf properties that want in-region residency.
Who owns the data — and where does GDPR fit?
You do: you are the data controller, AURI the data processor acting on your instructions. The GDPR toolkit is built into the product — consent capture with withdrawal, anonymization, and automatic anonymization after the retention window (24 months by default).
Can AURI integrate with our own systems?
Yes. A documented REST API (v1, 11 endpoints, Bearer authentication, OpenAPI spec) covers services, availability, bookings, reports, and metrics — and because every client runs a dedicated instance, custom work can be scoped as part of an implementation. PMS connections are covered on the integrations page.
What happens to our data if AURI disappears?
You would keep everything. Your data is exportable at any moment in structured JSON and CSV — no ticket, no fee — and daily backups with point-in-time recovery run on your own instance the whole time. There is no lock-in to hold you; a handover is an export, not a negotiation. The contract side of leaving — the exit terms — is covered in straight answers.
Deeper detail — headers, timeouts, the build pipeline — lives in the full security statement.
Send us your hardest technical question.
The intro call is for the operator; the technical follow-up is for whoever asks the hard questions — hosting, residency, encryption, worst case. We answer specifically, in writing if you want it.
Same-week slot forward this page to your IT team we answer specifics