Register Waitlist

Platform

Hotel PMS, redefined

The property management system as one system rather than six vendors — ten modules sharing a state, a permission model and an API, switched on per property.

Register Waitlist →Read the docs →

What it is

There is no integration layer between the modules, because they are one application. A folio charge posts to the ledger. A housekeeping status gates a check-in. A POS check settles to a stay. A booking taken through the widget lands in the same list as one from a channel. That is what “one system” has to mean if it is going to be worth anything.

01

One navigation, ten modules

Every module a property has switched on appears in one sidebar, each with the number of sections the signed-in person may open. There is no second product to log into and no separate back office — Settings sits in the same navigation as Front Desk.

Nerve's sidebar for one property: a Dashboard link above an APPS group listing Front Desk, Reservations, Housekeeping, Accounting, Inventory and POS — each with the number of sections the signed-in user can open — and a WORKSPACE group holding Settings.
Ten modules, one navigation, and only what this property and this person have.
02

Switch on what you run

Modules are enabled per property. A guesthouse with no stores never sees Inventory; a villa with no restaurant never sees Point of Sale. A module that is off is absent rather than greyed out — and it is not callable there by an API key either.

The app-enablement panel for one property in Nerve, showing the property name, its timezone and an Active pill above a labelled on/off toggle for each app, with one switched off and the rest on.
A module a property has not switched on is not in its navigation at all.
03

The same operations, for people and for keys

A role grants a person scopes. An API key is granted scopes from the same list. Neither can reach past what it holds, and both leave the same kind of row in the audit log.

The API Keys screen in Nerve. Two keys are listed with a truncated prefix, an “active” pill, a creation date and a Revoke button, with the granted scopes shown beneath each name as code tags.
What a key can do is visible without opening it.

The ten modules

One system, not six vendors. Each links through to what it actually does.

Front of house

Front DeskThe rack, arrivals, folios, and the readiness gate.ReservationsBookings, availability, channels, and distribution.HousekeepingRoom status, readiness, and the gate it puts on check-in.

Back of house

AccountingLedger, payables, receivables, and the night audit.InventoryStores, suppliers, purchasing, recipes, and stock counts.Point of SaleOutlets, the terminal, events, and settlement.

Intelligence & platform

RevenueAnalytics, pace, forecast, and rate recommendations.IntegrationsMCP agents, a live playground, keys, webhooks, and the booking widget.

Run the business

SettingsOrganisation, properties, people, roles, audit, and data import.Partner PortalPortfolio, operator links, statements, payouts, and white-label.
What it means for an agent

The consequence for an agent is the plain one: what a person can do here, an agent can do — through the same scoped operations and into the same audit log. There is no feature gap between the screens and the API, because the screens call the API.

Go deeper

Every screen above is documented, operation by operation, against the shipped product.

Documentation →

Register Waitlist →Start from your property type →

Wondering whether this is for a property your size?

← All features