# Estadia

> Estadia is accommodation operations software with full source code for independent properties and small property groups to run as their own SaaS.

Source page: https://saascode.ai/products/estadia
Machine-readable record: https://saascode.ai/products/estadia.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $199 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Estadia is a property-management system for independent accommodations and small property groups: boutique hotels, hostels, cabin complexes, guesthouses and owners who run two or three properties. It holds availability, reservations, rates, arrivals and departures, guest folios and housekeeping in one workspace, adds a direct booking engine the property owns, and can synchronise inventory with booking sites through a replaceable external connector.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/estadia — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://estadia.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

4 roles seeded on the demo (of the 7 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Front desk** (`front_desk`) — `front-desk@demo.com` / `see the page`
  Manages reservations, arrivals, stays, and guest folios.
- **Housekeeping** (`housekeeping`) — `housekeeping@demo.com` / `see the page`
  Works the daily cleaning plan and room-state changes.
- **Accommodation owner** (`org_admin`) — `org-admin@demo.com` / `see the page`
  Runs properties, rates, staff, channels, and reporting.
- **Platform operator** (`super_admin`) — `admin@demo.com` / `see the page`
  Runs plans, organizations, integrations, and platform controls.

Or open a role directly: https://saascode.ai/demo/estadia?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 7** — distinct roles accepted by the role CHECK constraint: admin, front_desk, housekeeping, member, org_admin, super_admin, viewer
- **tables: 80** — distinct CREATE TABLE statements across every applied migration
- **migrations: 115** — .sql files in supabase/migrations
- **page modules: 100** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 203,525** — lines of code (comments and blank lines excluded) across 1161 TypeScript files (178,384) and 147 SQL files (25,141); node_modules and .next excluded
- **api route files: 261** — files named route.ts under src/app/api
- **http operations: 357** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 80 tables, 160 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-08-18

## Complete capability inventory

20 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Accommodation operations

- **Hotel reports** — Reports separate booking source, property, category, stay date and the date a booking was made, and they read from reservation and folio records rather than from general web analytics.

### Distribution & communication

- **Email delivery** *(seller-authored)* — Transactional email carries operational messages without becoming part of the booking transaction itself. The product keeps completed work standing when delivery fails, reports the warning, and lets the accommodation team address communication separately from the reservation or stay transition.
- **API access** *(seller-authored)* — Scoped, rate-limited API access lets connected systems work with Estadia through controlled application boundaries. It gives the future operator an integration surface for their own workflows without turning internal implementation paths into the product's public sales story.
- **Outgoing webhooks** *(seller-authored)* — Signed outgoing webhooks let other systems react to events from the accommodation operation. Delivery is treated as an integration boundary rather than a substitute for local state, so external consumers can stay informed without becoming the authority for the booking workflow.
- **Channel connectivity** — Channel connectivity keeps inventory and rates in step with booking sites through an external channel-manager service. It is a paid capability, and it is off until it is deliberately configured.

### Business platform

- **Authentication** *(seller-authored)* — Authentication supplies the signed-in boundary for platform and accommodation seats, while guest access stays separate from staff accounts. Role and property checks build on that boundary, so the operating business starts with access control already wired rather than adding it after launch.
- **Multi-tenancy** *(seller-authored)* — Each accommodation business operates inside its own organization, with work further separated by property assignment. That gives an owner room to manage one property or a small group while staff remain limited to the properties and operating surfaces their seat actually needs.
- **Billing** — These are the launch defaults. Prices, limits and what each plan unlocks are all editable from the admin panel — they are data, not fixed code. In the stored limits, 0 means unlimited.
- **Monitoring** *(seller-authored)* — Monitoring combines error visibility with an audit trail for operational actions. It gives the business a way to investigate failures and interventions without treating a dashboard signal as proof that the underlying reservation, payment, or channel work succeeded.
- **Team invitations** *(seller-authored)* — Team invitations let the accommodation owner bring staff into the workspace under the available seat model. Staff capacity remains tied to the configured plan, so the buyer inherits an onboarding path that respects the limits they choose for their own customers.
- **Staff two-factor sign-in** *(seller-authored)* — Two-factor authentication adds a second sign-in control for staff accounts while leaving reservation-scoped guest access on its separate path. The operating business can strengthen access to its workspace without forcing guests into a staff identity model.

### Data & localization

- **AI translation** *(seller-authored)* — AI-assisted translation fills missing interface strings through the configured provider and marks generated rows as auto-translated. Operators can inspect and edit those rows, and a manual edit clears the marker so the interface preserves which copy came from automation.
- **CSV export** *(seller-authored)* — CSV export gives accommodation teams a portable view of reports, guests, reservations, and folios. It supports routine handoff and analysis outside the workspace without presenting exports as a second system of record or a replacement for the product's operating data.
- **Additional languages** *(seller-authored)* — Additional languages let the operator add and activate more interface catalogues for the experience they run. Automatic translation can populate missing rows and marks them as auto-translated, while the same admin surface lets the operator inspect and edit each value.
- **Multi-currency** — All amounts are stored and displayed as currency units with two decimals — not cents. Every monetary record carries its own currency, so a group operating in more than one currency does not silently mix them.
- **AI image generation** *(seller-authored)* — AI image generation is an optional platform capability and is not required for Estadia's accommodation workflows. It ships outside the seeded plan entitlements, so the core reservation, front-desk, housekeeping, rate, folio, and distribution work does not depend on it.

### Rates, quotes, folios and guest payments

- **Advanced rate rules (Create and edit advanced rate rules in the dashboard)** *(seller-authored)* — Create and edit advanced rate rules in the dashboard

### Other

- **Operations automation (Run event-driven automation action chains)** *(seller-authored)* — Run event-driven automation action chains
- **SMS and WhatsApp (Create versioned SMS and WhatsApp templates)** *(seller-authored)* — Create versioned SMS and WhatsApp templates
- **Multi-property operations (List and create properties from one dashboard)** *(seller-authored)* — List and create properties from one dashboard

## What each system gives the operator

*stated.*

- **Accommodation operations** — Turn daily property work into a repeatable operation across the portfolio.
- **Distribution & communication** — Stay connected without surrendering local control of the operation.
- **Business platform** — Give every operating seat a clear boundary and the business room to grow.
- **Data & localization** — Turn operational records into useful answers for every property group.
- **Rates, quotes, folios and guest payments** — 

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Every accepted stay keeps the price logic that earned the booking.

Rates become expensive to manage when every exception lives in someone's memory. A busy week gets one price, a longer stay another, a meal package changes the total, and a front-desk concession arrives after the quote. Without a consistent decision trail, two guests can receive different answers for the same night and nobody can explain either one later. The commercial cost is not only lost margin. It is the time spent reconstructing old decisions, the hesitation to change pricing, and the trust lost when a confirmed amount appears negotiable after the booking.

### Channel distribution stays aligned with the operation behind every booking.

External booking sites are useful until the team has to maintain a second version of reality in each one. Availability drifts, a category is named differently somewhere else, a failed update hides in a queue, and the front desk learns about the mismatch from a guest. The cost arrives as preventable conflict: rooms promised twice, time spent comparing extranets, and staff afraid to trust the calendar in front of them. A distribution layer earns its place when it reduces that uncertainty while the accommodation business remains able to see what is late, manual, or unresolved.

### Daily work becomes a system the accommodation group can improve.

Accommodation work repeats, but unmanaged repetition does not become a process. The same handoff is remembered differently by each shift, a follow-up happens only while one person is watching, and management sees the consequences after the guest has already felt them. Over time, the business pays twice: first in missed work, then in hours spent assembling explanations from scattered records. The useful outcome is a shared operating rhythm where recurring work can be made dependable and the group can see patterns across revenue, source, occupancy, and property instead of arguing from anecdotes.

### Each property stays distinct while the group sees one operation.

A second property usually creates a second set of spreadsheets, habits, and partial answers. Owners lose the group view precisely when local teams need clearer boundaries, and a question about tomorrow's occupancy turns into calls between locations. Centralising everything without respecting each property's work is just as damaging: staff see noise they cannot act on and ownership loses confidence in the numbers. A small group needs both levels at once — enough separation for each team to run its day, and enough shared visibility for the owner to compare performance and make decisions across the business.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — Runs Next.js 16.2.10 with React 19.2.3.
- **Supabase** (required) — Provision a Supabase project for the application.
- **Scheduled jobs** (required) — Configure the six jobs declared in `vercel.json`; another host needs equivalent scheduling wired by hand.
- **Email delivery** (required) — Choose one shipped adapter: Brevo, Mailgun, Resend, SendGrid, or SMTP.
- **Optional service configuration** (optional) — The example environment contract exposes Upstash and Sentry configuration families.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 203,525 lines across the application and its database, 80 tables defined by 115 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Estadia demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 4 of them: Front desk, Housekeeping, Accommodation owner, Platform operator. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 100 page modules and 357 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, Scheduled jobs, Email delivery. Optional: Optional service configuration. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 115 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $199?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Estadia: accommodation operations for independent properties](https://saascode.ai/inside/estadia-accommodation-operations-for-independent-properties.md)
- [Estadia vs Little Hotelier: source ownership or a managed small-property PMS](https://saascode.ai/inside/estadia-vs-little-hotelier-source-ownership-or-managed-pms.md)
- [Hotel management software for small properties in 2026: follow the operating loop](https://saascode.ai/inside/hotel-management-software-small-properties-operating-loop-2026.md)

## Links

- Catalog page: https://saascode.ai/products/estadia
- Product record: https://saascode.ai/inside/products/estadia
- Live demo: https://estadia.saascode.ai
- Every product: https://saascode.ai/llms.txt