Self-storage management software: one operation, one connected record.

The rental lifecycle, end to end. Staff manage customers and units, hold reservations, complete move-ins, schedule or complete move-outs, and transfer a customer between units. Every operation is tied to an authorised facility context, so choosing a site from a menu is never the same thing as being permitted to act on it.

Inventory can be read three ways, because different jobs need different views. A list carries detailed administration, a status board suits scanning, and the interactive facility map connects the drawn layout to live unit state, so finding a unit works the way staff experience the site. One filter set drives all three.

Customer accounts join rentals to documents, communications, invoices and payments, so a balance is read with its history attached rather than as an isolated number. The same records serve the public booking flow and the customer portal, which removes the hand-off between a website, a payment tool and the console.

• Customers, contacts, documents, custom fields and a nominated billing contact for financial notices.
• Units, unit types, pricing plans, status colours, bulk creation and a per-unit event history.
• Reservations, move-ins, move-outs and unit transfers that carry the balance with the customer.
• Invoices, allocation, proration, Stripe card payments, saved cards, autopay, refunds and disputes.
• Email, SMS and print from one template catalogue, with batches, delivery tracking and consent state.
• Rent roll, occupancy, revenue, move-in and move-out reporting, saved and scheduled, exported as CSV or PDF.

More than a facility selector in the header. Staff access is authorised against the facilities assigned to the signed-in person, and a record from one site is not exposed merely because someone supplies its identifier. Regions and organisation grouping sit above the facility, and cross-site views never widen a role.

Permission is enforced per column rather than per page. A role can see units and status across the list, the board and the map and never see a balance or a tenant contact, which is a distinction that closed a real leak on the site map. Enterprise SSO and fully custom role definition are planned, not available, and larger groups should weigh that before committing.

Payment operations are idempotent, so a retry or a re-delivered webhook is not a second charge. Allocation, proration, reversals, refunds and disputes each have explicit records. Past-due accounts move through defined stages with stage fees, collection notes, promises to pay and lockout scope, and one operations queue computes the day of work.

The ledger is append-only, enforced by a database trigger as well as in the application, so a correction appears as a reversal and a new entry rather than as a quiet edit to history. Four financial test files are frozen by checksum, so no later build can weaken them invisibly. Accounting periods close, and a posting into a closed period is refused.

Unit transfers show the principle most clearly. A customer may change the space they occupy, but the debt belongs to the customer ledger rather than to the rental, so it survives the move. An arrears or lockout override is capability-checked and audited with a reason rather than hidden inside a generic edit.

Yes. The booking flow shows live unit-type pricing, sizes the requirement, holds a unit, verifies the email address, creates the account, collects KYC documents and takes a first card payment through Stripe. The resulting invoice, rental and unit allocation land in the records staff already work from. Booking is refused at a site whose storage agreement is not published, and the customer is told so rather than charged.

Afterwards, fifteen portal routes let a customer see units, balances, invoices and payments, pay a balance, manage a saved card and autopay, upload KYC documents, read and sign an agreement, transfer, add a unit and start a move-out. Agreements are versioned, refuse to publish with an unresolved placeholder, capture multiple signers, log every signature event and seal the document with a hash.

Independent and growing operators that need a serious operational record without losing visibility as they add facilities. Container, indoor and mixed-format sites model units and layouts while finance and customer work stay in one system. Existing data arrives through a six-stage import pipeline with reconciliation across four entity types.

That pipeline refuses live tenancies by design, so a migrated site arrives with customers and units but no active rentals, and eight record types are refused with the reason named in code. No price, customer count or review appears on this page, because none of them has evidence attached to it yet.

Direct Debit. A bank-debit provider connects through the integration layer, but no charging adapter exists behind that connection, so nothing can be collected through it. That is a second-gateway decision nobody has taken rather than a sprint waiting to happen, and until it is taken the product is honestly described as card-only.

One tax path is also wrong, and it is not papered over elsewhere: a site that has configured tax on rent collects none on a first month booked through the public booking flow. The rest of the tax model resolves per scope and per category with every change audited. Complete online-booking tax handling is not a claim this product makes.