Everything you need to run spaces, in one place

One install supports four ways to operate. Pick your purpose during onboarding and the dashboard, wording, default term, and billing cycle all reshape around it.

• Long lease: expiring contracts, this month's collections, long-vacant spaces, 12-month revenue trend
• Monthly rental (parking·storage): space assignment board, overdue, new/terminated
• Short stay: today's check-in/out, occupancy, 30-day booking calendar
• Hourly rental (meeting rooms): today's slot bookings, slot utilization, peak hours

Pages with different purposes can run together on one site, each with its own theme and data (hybrid).

Everything is defined by three core entities.

• Place: the smallest rentable unit — a room, spot, or cell — with a floor label, gross/effective area, and a shared-cost ratio.
• Counterparty: an individual or business; registration and resident numbers are stored masked.
• Contract: links a place to a counterparty with deposit, monthly rent, monthly maintenance, and a term.

A space becomes 'occupied' automatically while an active contract exists, and a contract expires automatically once its end date passes.

Invoices are never generated automatically. The moment you press [Generate this month's invoices] on the dashboard, the data is combined into a snapshot.

• Active contracts + this month's meter readings + issuer/bank details become one batch plus one invoice line per counterparty.
• Each line preserves the details at issue time, so already-issued invoices stay intact even if counterparty info changes later.
• Issue → email → confirm payment are handled per line, and a PDF invoice can be downloaded.
• If a batch for the same month already exists, it asks before overwriting.

Provider charges such as electricity and water are split across counterparties precisely.

• Define meters and enter readings each month; usage (this month − last month) is computed automatically.
• The provider total is distributed per line by usage and shared-cost ratio.
• Each line is rounded to the currency's step and the remainder is absorbed into the largest line, so line total = provider charge exactly.
• Server and screen use the same rules, so displayed and stored amounts always match.

Describe a building in words and AI drafts the floors and rooms.

• A free description plus structured fields (floor count, area, features) compose the prompt.
• Multiple AI providers fall back by priority (Anthropic → OpenAI → Gemini …), and responses are strictly validated against a server schema.
• Refine the result in a canvas editor with drag, resize, and grid snapping; confirm to commit it as real space data.
• Generation progress is delivered in real time.

Every dashboard card is abstracted as a registered widget.

• Purpose-specific preset widgets are laid out automatically (KPI, chart, list, board).
• Reorder cards by dragging, or swap one for a different visualization from the gear menu.
• The server generates real-data preview images, so even unplaced widgets can be previewed.
• Frequently read data is cached, removing remote-DB round-trips on repeat loads.

Visitors can book or inquire straight from public pages.

• Short-stay and hourly bookings are confirmed instantly after a conflict check (live quote, payment offline).
• Intakes like vehicle registration, monthly renewal, viewing requests, and agent leads land in an inbox.
• The operator changes status in the inbox and applies it from the existing admin screens.
• Partner-only service requests are defined and managed as a two-level topic tree.

Mail, SMS, e-signature, tax invoicing, and AI connect through standard adapters.

• Mail 6 · SMS/notification 21 · e-signature 5 · tax invoice 6 · AI 5 — 43 in total.
• Providers are ordered by priority and fall back automatically on failure.
• API keys are stored encrypted, and a connection test verifies real reachability from the admin.
• In development, mock adapters keep everything running, so the pipeline works even without keys.

The foundation for global rollout and reliable operation is in place.

• 8 front-end languages, 4 admin languages, and per-currency rounding (19 currencies) for amounts.
• Compose public pages freely from blocks like this one, and translate every locale at once with the AI translation wizard.
• Five roles (anonymous, member, partner, staff, admin) and a staff action audit log.
• Sessions, cache, and broadcasting run on Redis, designed to minimize remote-DB round-trips.