Real Estate Management
Properties, contracts, instalment schedules and payments for developers and agencies. See what's overdue at a glance, track expenses and suppliers, and run reports — in English, Albanian and German.
Platform · Shared foundation
Every business app needs the same plumbing: sign-in, companies, users, roles, permissions, settings. We built it once. The platform gives each customer a tenant that owns one or more companies, lets admins decide who may view, create, edit or delete what, and switches products on for a tenant, with optional start and end dates, from one admin screen. Our property, hotel and file apps run on it, and a new app generated from its template starts with that wiring already done.
What it does
Token sessions with refresh, sign out everywhere, password reset, and a lockout after repeated failed attempts.
A tenant owns many companies. Every record carries its tenant and company, and shared services enforce the boundary.
A matrix of view, create, edit and delete for each role across dozens of resources.
Switch each product on or off for a tenant, with optional start and end dates. It is access control, not billing.
Companies can register or apply through a public form, and staff review the application before access is switched on.
Admins define extra modules for a tenant — text, number, date, yes/no, select and relation fields — and add custom fields to existing records.
Apps fetch their settings from one place at start-up, secrets masked and encrypted, and a new app is generated from a template with the wiring done.
How it works
A tenant is created with its first company and a first manager.
Switch on the products the tenant should have, with dates if you want them.
Define roles and the permission matrix, and add custom fields or modules where the standard records fall short.
New apps register with the platform when they start and share its sign-in.
Who it’s for
Business Platform is designed and built by Valton Sejdiu and Ardit Grajqevci — the two founders of VA Org, who also write the code. Meet the team
Questions
Every record carries its tenant and company, and shared services enforce it. That is row-level separation, not a separate database for each customer.
No. Product switches are access control with optional dates; there is no billing or plan management in the platform.
Sign-in is by email and password with refresh sessions. Single sign-on providers and two-factor enrolment are not part of it.
Yes. If you are planning a product that serves many companies, start with the inquiry form and tell us who the customers are.
More from us
Properties, contracts, instalment schedules and payments for developers and agencies. See what's overdue at a glance, track expenses and suppliers, and run reports — in English, Albanian and German.
A document store with folders, version history, a 30-day trash and expiring share links — and one place where documents from your other business apps appear, organised by system and record.
How we'd build yours
Internal software shaped around how your business actually runs — not how an off-the-shelf tool wishes it ran.
A product real users can log into. We cut scope honestly instead of padding an estimate, and it's running on a live URL in week one.
Read more
The trade-offs between row-level tenancy and a database per customer, how to enforce isolation in code, and what we chose for our own business apps.
Send a short note. One of the founders will reply within one working day and show you around.