Pricing
Not per seat. Not per door. Not a slice of every invoice you raise, and nothing extra for giving your corporate clients and your landlords their own portal. Three headline numbers, eleven allowances behind them, and every one of the eleven carries the sentence that says exactly what it counts.
The three levers
A property is a building you have taken. A user is a member of your staff who signs in. A space is a room, a partition or a bed — the thing you actually let. Everything else in the product is unlimited by these three.
Properties that are not deleted and not marked exited.
Bars are drawn linearly. Base really is that thin next to Premium — a scale that flattered it would be a chart that had decided to sell rather than to inform.
Active internal users. Portal users for your tenants and corporate clients are not counted.
Bars are drawn linearly. Base really is that thin next to Premium — a scale that flattered it would be a chart that had decided to sell rather than to inform.
Rooms, partitions, bedspaces, whole units, studios and cabins — every status, including under fit-out and out of service, because you are storing them. Parking, storage and amenity spaces are not counted.
Bars are drawn linearly. Base really is that thin next to Premium — a scale that flattered it would be a chart that had decided to sell rather than to inform.
The quota explorer
A pricing table tells you what a package costs. It cannot tell you what a limit is, because a limit is not a number — it is a refusal that happens at a particular moment to a particular person. Drag the three sliders to the estate you actually run, then pick a smaller package and watch what it would have said.
Spaces is what puts it there: 1,800 needs Pro’s 3,000.
Property P&L, preventive maintenance and advanced reporting.
Room for 4 more.
Counted as Properties that are not deleted and not marked exited.
Room for 11 more.
Counted as Active internal users. Portal users for tenants and clients are not counted.
Room for 1,200 more.
Counted as Rooms, partitions, bedspaces, whole units, studios and cabins — every status, including under fit-out and out of service, because you are storing them. Parking, storage and amenity spaces are not counted.
Everything fits on Pro — AED 1,799 a month, or AED 17,990 a year, which is two months free. 14-day trial, no card. Pick a smaller package above to see what it would refuse.
30 of 36 on Pro. Features are cumulative, so the matrix is one line rather than a grid of ticks.
The figures in the dial are the seeded defaults, transcribed. The package cards and the allowance table further down this page are read from the live catalogue — the same rows the platform console edits — at the moment you load the page. Where the two disagree, the live ones are the ones you would be sold.
The capability list is a comparison, not a lock. A package definition carries thirty-six capability switches, and the dial groups them by the tier they were designed to arrive at. In the product as it stands, no part of the API refuses a call because of one of those switches — the eleven allowances are enforced, the capability switches are not. Read the dial’s “included on Pro” and “needs Premium” labels as the tier a capability was drawn for, then, rather than a gate that would stop you: today none of them would refuse you anything. What you are buying is size.
The catalogue, live
These prices and allowances are read from the product itself as this page loads, not maintained in marketing copy. The console edits one set of rows and both the website and the customer’s own subscription screen change together.
AED 199a month
or AED 1,990 a year — 2 months free
One property, three users, two hundred beds. Everything you need.
14 days, no card. The trial runs the Pro capability list at twice the Base allowances.
AED 599a month
or AED 6,600 a year — 1 months free
Corporate contracts, the cost side, and the API. For a growing portfolio.
14 days, no card. The trial runs the Pro capability list at twice the Base allowances.
AED 1,799a month
or AED 17,990 a year — 2 months free
Property P&L, preventive maintenance and advanced reporting.
14 days, no card. The trial runs the Pro capability list at twice the Base allowances.
AED 4,999a month
or AED 54,990 a year — 1 months free
Unlimited customers and portal seats, single sign-on, white label.
30 days, no card. The trial runs the Pro capability list at twice the Base allowances.
By quotemonthly or annual, whichever you sign
Larger than Premium, or shaped differently. A private package is built for your organisation alone, starting from the nearest published tier, with only the terms being negotiated changed — so a bespoke deal is a short list of differences rather than a blank sheet.
A custom package is negotiated with us. There is no self-serve route from this page to a quote.
Every package includes the whole product: bed-level inventory, the head-lease cost side, corporate contracts and pooled lines, post-dated cheques, deposits, maintenance, the three portals and all forty-six reports. What changes between packages is how much of it you can hold.
Eleven allowances
A figure that looks wrong is a dispute when nobody can say what it counted, and a conversation when everybody can. So the counting sentence sits beside the number here, on your subscription screen, and in the tooltip on the usage bar.
| Allowance | At the limit | Base | Starter | Pro | Premium | Counted as |
|---|---|---|---|---|---|---|
| Properties | Refused | 1 | 3 | 10 | 40 | Properties that are not deleted and not marked exited. |
| Users | Refused | 3 | 8 | 25 | 100 | Active internal users. Portal users for your tenants and corporate clients are not counted. |
| Spaces | Refused | 200 | 750 | 3,000 | 15,000 | Rooms, partitions, bedspaces, whole units, studios and cabins — every status, including under fit-out and out of service, because you are storing them. Parking, storage and amenity spaces are not counted. |
| Occupants | Refused | 250 | 1,000 | 4,000 | 20,000 | People currently resident. Prospects and checked-out occupants are not counted. |
| Corporate customers | Refused | 10 | 50 | 250 | No limit | Active company customers. Individual customers are not counted. |
| Portal seats | Refused | 50 | 250 | 1,500 | No limit | Active portal users across the tenant, corporate and landlord portals. |
| Webhook endpoints | Refused | Not included | 2 | 10 | 50 | Configured webhook endpoints, enabled or not. |
| Document storage | Allowed to run over | 5 GB | 25 GB | 100 GB | 500 GB | Total size of every file you have uploaded and not deleted. |
| API calls a month (published but not counted) | Allowed to run over | Not included | 25,000 | 250,000 | 2,000,000 | Public API calls this calendar month, resetting at month start in your own timezone. |
| WhatsApp and SMS credits (published but not counted) | Allowed to run over | Not included | 500 | 3,000 | 15,000 | Successful dispatches this month. A failed send does not consume a credit. |
| Data retention | Never refused | 12 months | 24 months | 60 months | Kept indefinitely | How long audit records and documents are kept before the purge job removes them. Nothing is ever refused on this one. |
Properties, users, spaces, occupants, corporate customers, portal seats and webhook endpoints. The create call is blocked outright with 402 QUOTA_EXCEEDED. Nothing is half-created and nothing is queued.
A hard limit that sometimes lets one through is worse than no limit, because you cannot tell which number is real.
Document storage, API calls and WhatsApp credits are metered rather than refused. In the product as it stands an overrun on a metered allowance is simply allowed: there is no overage charge, and no metered metric is billed for going past its figure.
Said plainly because the alternative is a surprise line on an invoice, and a surprise line on an invoice is how trust in a bill ends.
Data retention is how long audit records and documents are kept before the purge job removes them. It is a term of the package rather than a wall: no call is ever blocked because of it.
Retention is the difference between a package and a filing policy, and it belongs on the price list rather than in a settings screen nobody opens.
The wall, and the door in it
Twenty-two past eleven, a contractor’s men are at the gate, and somebody is building out Block C. This is the whole sequence, in order, with nothing left out.
Before counting anything, the database takes a lock on the pair — your organisation and that one allowance. Two people adding beds at the same instant queue behind each other rather than each reading the same stale figure.
Not a check followed by a write. One transaction: if the count fails, the beds were never created, and if the beds are created the count had already passed. There is no window in which twenty staff jointly land you fifteen beds over the package with nothing reporting an error.
Not “limit reached”. The response carries the allowance, what you hold, what the package allows, how many over you would be, and both routes through — worked out by the cost of covering the shortfall rather than by sticker price, so two five-user packs beat one ten-pack when the ten costs more than twice as much.
The Subscription screen in your workspace sets add-on quantities and moves the package up or down. Only the owner sees the buttons; your finance staff see the whole table without them, so the person who needs the numbers to justify the upgrade can pull them without holding the authority to make it.
Adding 340 would take you to 752 spaces; your plan allows 750.
A month, on top of Starter. The ceiling becomes 1,000 and Block C finishes building.
A month. Three thousand spaces, ten properties and twenty-five users — the whole tier rather than the shortfall.
Sample figures, on Starter’s seeded allowance of 750 spaces. The shape of the response — the allowance, the four counts, and both priced routes out — is what the product actually returns.
Add-ons
Seven add-ons, bought from your own subscription screen, each raising one allowance. They add to whatever you already had — including anything negotiated. An operator who agreed 500 beds and then buys a 250-pack has 750, not 250: the deal you struck is not quietly overwritten by a purchase.
One more property.
Five more internal users. Portal seats are separate and are not touched.
250 more rooms, partitions or beds.
25 GB more document storage.
1,000 more WhatsApp or SMS messages a month.
Ten more webhook endpoints.
We import your existing portfolio, contracts and occupants.
Add-on prices are the seeded defaults, transcribed from the catalogue rather than read live: the packages, their prices and their limits are editable in the console, and the add-on catalogue is not. Your own subscription screen is the figure that binds.
Going down as well as up
Moving to a smaller package is checked against what you actually hold, and the check runs on a preview button rather than on the change. You get the whole list at once — not “deactivate four users”, then, an afternoon later, “and you also have too many properties”.
Add-ons and any negotiated limit are counted in, so a package you have extended does not report a blocker you have already paid to remove. The same guard runs on our side of the console, so nobody can move you down into a state your data cannot fit.
Sample portfolio. Nothing has changed on the account — this is what the preview button returns before you commit.
The trial
Whichever package you pick at signup, the trial runs the Pro capability set held at twice the Base allowances. You get to see what corporate contracts and the head-lease cost side actually look like before paying for them, and you cannot accidentally build a three-thousand-bed portfolio inside a free trial and then be stuck inside it.
Twice the Base allowances, computed from the live catalogue. Capabilities are Pro’s — including the corporate portal, pooled contract lines and the cost side — on every package.
A nightly job marks trials ending within three days, and from that point your subscription screen carries the notice and the date.
Not straight to suspension. Fourteen days in which you keep reading and keep working the contracts you already hold.
Sign in, read everything, export everything. Nothing is deleted at the end of a trial and no data is held back to force a decision.
Converting sets a monthly or annual term and the account becomes active. We can also extend a trial — by up to 180 days — if you are mid-mobilisation and the timing is wrong.
The lifecycle
A late transfer from your accounts department must not take a labour camp’s occupancy records offline. Seven states, and the only one that stops you signing in is the end of a long road rather than the consequence of one unpaid invoice.
Fourteen days, thirty on Premium. The Pro capability list, held at twice the Base allowances.
Everything your package allows, and an invoice on the same day each period.
Nothing changes yet. You are chased at three, seven and fourteen days past the due date, and the rung reached is written onto the invoice.
Read everything, and keep working the contracts you already hold. New properties, beds and contracts are refused until the invoice is settled.
Sign in, read everything, export everything. Nothing is deleted and nothing is hidden.
You keep working to the end of the period you have paid for.
The only state in which sign-in stops. It is the end of a long road, not the consequence of one late transfer.
The rung the chase reached is written onto the invoice itself rather than recalculated from a date. A job that runs late chases you once, not three times, and a customer who pays on day eight is never chased on day fourteen.
The screen then shows what actually happened to that account, rather than what the calendar says should have.
Settling the last outstanding invoice returns the subscription to active in the same transaction as the payment. Not a nightly sweep, not a support ticket — the same instant.
Nobody should have to ring somebody to be let back into their own system after they have paid.
You can sign in, read every screen and export everything you hold. There is no state in which your occupancy records, contracts or invoices are hidden from you to force a payment.
Your data is never the hostage. It is the one thing about a billing dispute that should never be in question.
The billing run
Six scheduled jobs sit behind subscriptions, and their order is an argument rather than an accident: nobody gets a dunning notice for an invoice their own card was about to settle four minutes later.
The run is guarded twice — by its own key for the day, and by a lookup for an invoice already covering that period. Running the billing by hand after fixing something does nothing the second time and says so.
A double charge across every customer is the one billing bug you cannot apologise your way out of.
The package and add-on lines are frozen onto the invoice at the moment of billing, so it keeps its own figures even after the package it was priced from has been changed.
A bill that recalculates itself from today's price list is not a record of anything.
Payment happens on the gateway's own page. What comes back and is stored is a token, the brand, the last four digits and the expiry — there is no column for a card number anywhere in the database.
A stolen copy of the database is worthless to a card thief, and two callbacks for one order still produce one payment, so refreshing the return page cannot charge you twice.
What settles an invoice is the result the gateway posts back to the server. A browser returning from the payment page is never trusted on its own to mark anything paid.
It is the difference between a payment system and a screen that says you paid.
Negotiated terms
Not a note in a mailbox. A bespoke package starts from a published tier — pick Pro and every field fills with Pro’s real figures — and only the terms being negotiated are changed. It produces a numbered proposal showing two columns: what the standard package gives, and what yours does.
Illustrative negotiated figures against Pro’s live published ones. Accepting writes a private package for that organisation alone and sets the price and the limits on their subscription, in one transaction.
A quote can only be accepted after it has been sent, and never after it has lapsed. One live quote per organisation at a time, enforced by the database rather than by a screen remembering to check.
A year later, 'what did we actually sell them?' has an answer in the customer's own numbers, with a date on it.
Changing the price or limits of a package that has subscribers creates a new version and takes the old one off sale. Everyone on it stays exactly where they were until they are moved, and the console says how many stayed behind.
Raising Pro by two hundred dirhams must not silently change what every operator already on Pro signed up to.
Any one allowance can be raised or lowered for one organisation without moving them off their package, and every such change records what it was, what it became, who did it and why. Package changes, status changes, add-ons and trial extensions are kept the same way.
Six months later, 'why is this account on Pro with 250 properties?' has an answer rather than being folklore.
Getting in
Registering creates the organisation, your account, the owner role, the trial subscription and six sensible approval rules together. If any part of it fails, none of it happened.
Nobody ends up holding an account they cannot use and a support conversation nobody can resolve.
The company is created first and the email goes out afterwards, so a mail relay being down cannot undo a correctly created organisation.
An outage in something peripheral should never destroy something central.
Nothing is collected and nothing is authorised. Converting a trial to a paid subscription happens later, against an invoice that has actually been issued.
A trial that takes your card is a subscription with a delay on it.
Straight answers
Everything below is a real boundary of the product as it stands today. A pricing page that only lists what works is a pricing page you will find the edges of on your own, later, at a worse moment.
Yes, some are. The package definitions carry thirty-six capability switches, and eighteen of them are checked by the product: ask for one your package does not include and the answer names the capability and the cheapest package that has it. Size is enforced too — the eleven allowances, seven of them hard.
What is never gated is reading your own data. The checks sit on the acts that create and change things, so a package that no longer includes something does not hide what you already have: the records stay legible, and the button is what goes away.
No. Overage billing does not exist in the product. Document storage, API calls and WhatsApp credits are metered rather than hard, and an overrun on a metered allowance is simply allowed and never charged. There is no surprise line on an invoice, because there is no mechanism that could produce one.
Nine of them. API calls a month and WhatsApp credits are published on every package but are not yet counted — the figure displays and nothing is measured against it. The other nine are counted, and the seven hard ones are counted inside the transaction that creates the record.
Not yet. The cancelled state exists and is honoured, but there is no self-serve cancel button and no endpoint behind one — cancelling is a conversation with us today. Changing package up or down, and buying or removing add-ons, you do yourself from your subscription screen.
The three-day warning is computed nightly and recorded against your account, and it appears on your subscription screen. It is not sent as an email: the platform’s own notices — trial warnings, subscription invoices, custom quotes — are recorded rather than delivered by mail, and email delivery is configured per installation. Plan on seeing it when you sign in, not in your inbox.
Not for the subscription itself. Platform invoices are records in the console with their lines frozen on them; they are not rendered as PDFs and are not emailed. Your own tenant invoices — the ones you raise against your customers — are a separate system with its own document, including the bilingual tax invoice.
Tax on the platform’s own subscription invoices is currently zero, and there are no credit notes on a platform invoice. If your situation needs a tax treatment, raise it before you sign rather than after — tell us. The tax engine inside the product, for the invoices you raise against your own customers, is a different thing entirely and is fully built.
Not directly. A custom package is built by us in the console, starting from the nearest published tier, and it arrives as a numbered proposal with an expiry date. The route from here is the contact form — tell us the property count, the head count and the bed count and we will come back with the two columns.
No. Signing up creates your organisation, your owner account and your trial, and lands you in the workspace — it does not walk you through your first property, inventory, team invites or an import. The onboarding and migration add-on is the answer where a portfolio needs bringing across; it is quoted per job.
Usage is snapshotted hourly and anything past 80% of an allowance is recorded, then 95% again. Those thresholds are visible as usage bars on your own subscription screen. They do not currently raise a banner or an email of their own, so the honest advice is to look at the three bars on that screen when you are mobilising something large.
Only by starting a support session, which is read-only by default and needs a written reason. Write access additionally needs a ticket reference and your organisation name typed out in full. Either way the session lasts sixty minutes, shows a permanent red banner while it runs, and appears in your own activity trail rather than only in ours. Write mode still cannot void an invoice, delete a contract or close your organisation, and neither mode can read passport numbers, credit files, billing history or the audit trail.
Always. The package cards and the allowance table are read from the same rows the platform console edits, at the moment you loaded this page. If they cannot be read, the page says so rather than falling back to figures baked in at build time. The add-on prices and the quota explorer near the top carry the seeded defaults, and both are labelled where they appear.
Start
The limit that bites you first is on this page rather than being discovered on the night you are onboarding a camp. If none of the four published packages fits what you run, that is a conversation and not a dead end.