Estadia
Estadia is accommodation operations software with full source code for independent properties and small property groups to run as their own SaaS.
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.
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.
- Advanced rate rules (Create and edit advanced rate rules in the dashboard)
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.
- Channel connectivity
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.
- Operations automation (Run event-driven automation action chains)
- Hotel reports
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.
- Multi-property operations (List and create properties from one dashboard)
Three modes, and the label always tells the truth:
A connection is never a single green light. Its status is one of unconfigured, pending, connected, degraded, paused or failed, and alongside it the screen shows the last successful exchange, the current lag, the cursor position, mapping errors and the specific failed items with the repair action for each.
Inbound and outbound are queues, not calls. Reservations arriving from a booking site land in an inbox and are applied idempotently — the same message delivered twice does not create two reservations. Availability and rates going out sit in an outbox and are delivered per item, so one bad mapping does not stop everything else. Local confirmation never waits for either.
Two limits stated plainly:
The entry plan has no channel connectivity at all, and does not claim to prevent cross-site double bookings. Allocation across sites on that plan is manual, and the product says so rather than implying a sync it is not doing.
Core reservation work — calendar, reservations, front desk, guest folios, housekeeping, direct booking and email — is complete on every paid plan. What the higher plans add is distribution breadth, advanced rate rules and group-level rollups, not the ability to run the property at all.
The external channel provider's own fee is always separate and disclosed before a connector is switched on. It is never folded into the plan price.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 67 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 80 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · channel_connections · channel_inbox · channel_mappings · channel_outbox · communication_deliveries · communication_templates · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · folio_entries · folios · guest_payments · guest_portal_sessions · guests · housekeeping_tasks · inbound_webhook_events · inbound_webhooks · inventory_blocks · inventory_ledger · languages · marketing_audience_members · marketing_audiences · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · product_purchases · products · properties · provider_prices · push_devices · rate_plan_versions · rate_plans · rate_rules · report_templates · reservation_guests · reservation_nights · reservation_quotes · reservations · roles · room_categories · room_units · scheduled_tasks · seo_meta · staff_property_assignments · stays · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 4 required, 1 optional.
Runs Next.js 16.2.10 with React 19.2.3.
Provision a Supabase project for the application.
Configure the six jobs declared in `vercel.json`; another host needs equivalent scheduling wired by hand.
Choose one shipped adapter: Brevo, Mailgun, Resend, SendGrid, or SMTP.
The example environment contract exposes Upstash and Sentry configuration families.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.