# Hosting, stack and architecture

> For the business owner, in one paragraph: you choose where your booking system runs, and the code is yours in every case. If you do not want to run anything, we host it and keep it healthy. The rest of this page is for your IT team. Where…

Page: https://timerise.ai/infrastructure

For the business owner, in one paragraph: you choose where your booking system runs, and the code is yours in every case. If you do not want to run anything, we host it and keep it healthy. The rest of this page is for your IT team.

---

### Where the system runs

Ownership settles who the code belongs to. Hosting is a separate decision, and it is yours. We work in three models:

1. **Your cloud, managed by us.** The system runs in your cloud accounts, under your contracts and your billing. We handle setup, deployment, monitoring and keeping it healthy.
2. **Our cloud.** We provide the hosting and run everything on our side, billed by actual usage. Nothing to configure on your end. You can move to your own cloud whenever you decide: give us 90 days’ notice and we move the system and all your data for you.
3. **Your servers, your ops team.** The infrastructure is already configured by your people. We build the system and deploy it on what you have.

---

### The stack

We build on **Next.js on Vercel**, with **Supabase or Firestore on Google Cloud** as the database. That is the stack we recommend: quick to set up, costs that track usage instead of revenue, and a handover that takes hours rather than a migration project. We maintain it across every system we deliver.

If your organization runs on AWS, GCP, Azure, on-premise hardware or needs a specific data region (EU regions such as Frankfurt are available), we build there instead.

---

### What the system is made of

- **A data model** for your availability, resources, prices and rules: people, rooms, equipment, seats or vehicles, booked alone or together.
- **An API** for every function, REST or GraphQL, so your CRM, ERP, app or website can read and write bookings.
- **Booking pages** in your brand, on your domain.
- **An admin panel** for your staff: calendars, customers, payments and settings.
- **Integrations** with the tools you already use: CRMs such as Salesforce and HubSpot, payments through Stripe or Adyen (both PCI-DSS certified), and calendars.

---

### Security and data

- Data is encrypted at rest and in transit.
- It is stored in the region you choose.
- GDPR is part of the design. Where we host the system, we process data as your processor under our [Data Processing Agreement](/dpa).

---

### What your team gets at handover

- the source code in your own repository
- API documentation and TypeScript types
- a staging environment
- documentation of the system and how it runs

Any web developer can take it over. The code uses common technology and nothing in it depends on us.

---

### Moving data in

If you are on another booking system, rented or built for you, we move your bookings, customers and history while the old system keeps taking bookings. Before the switch we check every record against the source: counts and checksums, record by record. [How migration works](/blog/painless-data-migration-and-zero-maintenance-hosting).

---

### When you do not need any of this

If a ready-made tool does everything you need, stay with it. [Custom booking vs SaaS](/custom-booking-vs-saas) covers when owning a system starts to pay off.