A STATIC PROJECT SHOWCASE · NO LIVE BOOKINGS OR PAYMENTS

Open source. Independent by design.

Good stays.
Open systems.

An open-source booking system for cabins, campgrounds and places with a little more character. Own the guest experience. Make the code your own.

MIT-licensed code. Static examples here. A fresh deployment when you’re ready.

A cabin with room to breatheAn original illustration of a red cabin, forest and evening sun beside a lake.
Pinewood Flats● FICTIONAL EXAMPLE

A cabin by the water.

Lakeview Cabin · 3 nights · 2 guests

CA$140Illustrative nightly rate · before tax
YOUR BRAND HERE
Your code, your deploymentDirect booking foundationsMIT licenseAPI, CLI & MCP

Built around the place

Different stays.
The same open foundation.

A booking system should fit the property. Start with the parts you need, then shape the guest and operator experience around them.

01 / CABINS

A few cabins.
A better welcome.

Let guests choose a cabin, see available nights and understand the stay price. Keep seasonal rates, deposits and cancellation policies with your inventory.

NIGHTLY STAYS / SEASONAL RATES / DEPOSITS
02 / CAMPGROUNDS

Sites for tents.
Space for RVs.

Represent individual sites as bookable units. Use site categories, occupancy rules and turnover buffers without hard-coding the shape of your campground.

SITE INVENTORY / STAY RULES / ICAL FEEDS
03 / GLAMPING & RESORTS

Something a
little different.

Bring yurts, domes and mixed lodging onto one foundation. Give the front desk a shared view of reservations, service work and property operations.

MIXED UNIT TYPES / STAFF ROLES / OPERATIONS

From the guest to the front desk

See the stay.
Keep the details together.

The source connects booking inventory with staff workflows. This illustrated calendar shows the idea, using only fictional stays.

OpenStays Pinewood FlatsILLUSTRATIVE OPERATIONS VIEW

A little clarity for the week.

JUNE 18–24 / FICTIONAL SCHEDULE
Example only. These dates and reservations do not represent available inventory.
Unit18192021222324
Lakeview Cabin3-night stayArriving · 3 nights
Cedar Cabin4-night stayTurnover
Ridge YurtService blockArriving · 3 nights
RV Site 045-night stay
StayArrivalService
STATIC ILLUSTRATION / NO GUEST RECORDS

The illustration is explanatory, not an interactive product session. The source includes feature-gated staff workspaces; each requires operator configuration and acceptance.

Inside the source

A useful foundation.
With the edges made clear.

OpenStays brings the guest flow and property operations into one codebase. Run it for your own property and choose the services you connect.

01 / BOOKING

Availability with a transactional core

Booking holds and occupied nights change together. Rate rules, stay limits and turnover buffers belong with the property.

02 / PAYMENTS

Your provider, behind an interface

Stripe and Square integrations live in the source. Configure and verify your own checkout, webhooks and refund flow before taking money.

03 / STAFF

Operations with property-scoped roles

Front desk, housekeeping, maintenance, folios and night audit have feature-gated foundations, with explicit roles and audited actions.

04 / CALENDARS

Per-unit iCal, in and out

Import external calendar blocks and export unit calendars. Polling is not an instant cross-platform lock; staff still resolve conflicts.

05 / AUTOMATION

API, command line and MCP

Connect tools to the same booking rules. Scoped API keys, a standalone CLI and an MCP server provide an automation surface.

06 / OWNERSHIP

Property data outside the code

Your inventory, staff and guest records belong in your own backend. The public repository contains code and fictional fixtures.

An early-stage project, not a managed booking platform. Channel-provider certification, real inventory setup, provider credentials, security review, backups and live acceptance belong to each operator deployment. The experimental hackathon layer is separate from the reduced production profile.

Fork it. Shape it. Make room.

The code is open.
The next chapter is yours.

Use the MIT-licensed source as an alternative starting point to a closed booking system. This project site stays static. A new operational deployment starts with your own frontend, backend and configuration.

Your deployment / three deliberate layers
01 — Your guest experienceReact + Vite frontend · static hosting
02 — Your booking backendFresh Convex Cloud or self-hosted Convex
03 — Your chosen connectionsPayments · email · calendars · automation

THE PROJECT SITE USES NONE OF THESE SERVICES.

A few good questions

Open source.
Plain answers.

What the project does, what you can host, and what still needs an operator behind it.

What is OpenStays?

OpenStays is MIT-licensed, open-source booking and property-management software for independent lodging. Its source includes a guest reservation flow, availability checks, staff operations and integration points. This website is a static project showcase, not a hosted reservation service.

Who is OpenStays for?

OpenStays is designed for operators and developers working with cabins, campgrounds, RV sites, glamping, yurts and small resorts. Each operator runs a separate deployment and supplies their own property inventory, rates and policies.

Can I self-host OpenStays?

Yes. You can host the static frontend on Cloudflare or another static host and run a fresh backend with Convex Cloud or the self-hosted Convex backend. Fully self-hosted operation requires your own infrastructure, backups and maintenance. The project site needs no backend.

Is OpenStays free?

The OpenStays code is available under the MIT license, with no software license fee from this project. Hosting, payment processing, email and optional provider services can cost money. It is software you operate, not a free managed booking service.

Does it replace a booking platform or channel manager?

OpenStays is an alternative foundation for direct bookings and property operations. The source includes per-unit iCal import and export. Direct Airbnb, Booking.com and Expedia channel connectivity requires a separately configured provider, partner access and acceptance; it is not included as an activated service.

Can I make a real booking on this website?

No. All calendars, prices and reservations shown here are fictional examples. The project site has no booking backend. To accept real stays, deploy your own instance, configure inventory and providers, and verify the complete booking, payment, cancellation and recovery flows.