Platform

This is not a plan with features toggled on and off. Each client is a database of its own, with its industry's modules, its own people, and the portals it opens outwards.

One client, itemised

ajja_tenant_marisol

Hotel Marisol · Hotels

Active modules

Eight switched on day one. The hotel catalogue holds twenty-eight.

Database
One, only theirs
Tables
140, migrated from the start
Roles
Owner, manager, staff
Address
Own domain or subdomain
Portals
Guest and owner, by key

How a client is assembled

From signup to the first working day.

You pick the business once. Everything after that happens without anyone configuring it by hand.

  1. 01

    You pick the business

    Hotels, short-term rentals, cleaning, real estate, and four more. That choice decides everything that follows.

    Which leaves Hotel Marisol picks Hotels.

  2. 02

    The database is created

    A database of your own, with all 140 tables migrated from the start. Not a column in a table you share.

    Which leaves ajja_tenant_marisol exists, empty and theirs alone.

  3. 03

    The industry's modules switch on

    The industry's default set goes live, using the words that trade uses — listing, stay, work order.

    Which leaves Front desk, rooms, rates and the day's close open switched on.

  4. 04

    You are the owner, and you invite the rest

    Whoever signs up becomes the owner. Managers and staff come in by invitation, each seeing what their job needs.

    Which leaves One owner, two managers, six on the desk.

While this runs, you are on 14 days free: your card is checked without a charge, and you only pay on the 15th day after you subscribe unless you cancel first.

The same thing, your word for it

One module, six ways to name it.

The database stores one key. The screen shows the word your trade uses — not a translation, but the vocabulary you already use on the phone.

scheduling

  • Check-ins

    Local stays

  • Service Slots

    Cleaning

  • Pickup & Delivery

    Laundry

client_portal

  • Guest Portal

    Hotels

  • Buyer Area

    Real estate

  • Client Area

    Restaurants

  • Order Tracker

    Laundry

The keys stay in English in both languages: they are product identifiers, not copy.

Who sees what

Staff don't see the invoicing. And it isn't the menu hiding it.

Visibility per role is checked on the server. A hidden module doesn't appear in the navigation, and doesn't answer if someone types the address by hand.

Hotels, as it arrives

Module Owner Sees everything, without exception, and is the one who configures what the others see. Manager Configured module by module. Usually everything except what touches the house's money. Staff Starts from a set per industry — in cleaning they see the work orders and the route, not the invoices.
Front Desk Can see Can see Can see
Housekeeping Board Can see Can see Can see
Reservations Can see Can see Can see
Rate Plans Can see Can see Cannot see
Invoicing Can see Can see Cannot see
Analytics Can see Can see Cannot see
Legal & Compliance Can see Can see Cannot see

A starting point, not a sentence: the owner changes any row of this table from their own account. And what an employee cannot see also does not answer if they type the address by hand.

paid add-on

Advanced permissions control

For anyone who needs more than three roles, an add-on opens the matrix module by module, role by role. It switches on per client and joins the same monthly invoice.

€19/month, switched on by the owner from their own account.

And everyone outside the team

Guests, clients and owners come in by their own link, with no account to create and no app to install. Each link shows one thing: the stay, the proposal, the gallery or the property statement.

What connects to the outside

Your data comes and goes by roads you can see.

Nothing is held hostage. What comes in is logged, what fails can be replayed, and what is yours leaves in formats any other tool reads.

Working today

5
  • iCal calendars

    Both ways: import the calendars you already keep, and publish yours for whoever needs it.

  • Webhooks with replay

    Every event sent is logged with the response it got. Whatever failed replays with one click, without losing what happened.

  • Payments through Stripe

    Subscriptions, add-ons and what you charge your own clients, with the receipts to match.

  • Email and SMS

    Invitations, delivered proposals, guest notices. They leave the platform carrying your brand.

  • Our own API

    The whole application runs on the same API you would use. The owner creates read or write keys in the dashboard, and the reference is published.

Not connected yet

1
  • waiting on the portals

    Channel manager

    The plumbing is built — availability, rates and reservations coming in. What's missing is each portal's approval to connect the real accounts.

1 of these 6 are not ready, and saying so here is cheaper than you finding out after signing.

See this assembled around your business.

Create the account, pick the business, and the database and modules are up before your coffee is finished.

14 days free, with your card checked without a charge. Cancel before the 15th day after you subscribe and you pay nothing.