Live at its first venue

Runthevenue,notthepaperwork.

Regia is the system a marriage hall actually runs on. Bookings and advances, itemised bills, the expenses against each event and the deposits that follow, all in one place, with the books reconciled as you go.

01 / What it runsNIXE

Everyevent,endtoend.

Six modules covering the whole life of a booking, from the date being held to the month being closed.

01 / Module

Bookings

Every date, held in one calendar. Customer, hall rent, notes and status on the record, with up to three advance payments tracked per booking in cash, cheque or online.

  • Calendar view
  • Upcoming / completed / cancelled
  • Advance payments
02 / Module

Billing

Itemised bills built from your own categories: GST, cleaning, EB, water, gas, AC, room rent, generator. Per-unit rates where they apply. Export the finished bill as a PDF.

  • Configurable categories
  • Per-unit billing
  • PDF export
03 / Module

Expenses and deposits

Log what each event actually cost against your own expense heads, and record bank deposits against the account they landed in. The margin on a booking stops being a guess.

  • Per-booking expenses
  • Bank deposits
  • Multiple accounts
04 / Module

Dashboard

Revenue, expenses, net profit and booking counts at a glance, a monthly revenue chart with a year selector, and the upcoming events list the office actually works from.

  • Live KPIs
  • Monthly charts
  • Upcoming events
05 / Module

Reports

Consolidated financials across bookings and date ranges, so closing a month is a review rather than a rebuild from receipts and a notebook.

  • Date-range reports
  • Cross-booking totals
06 / Module

Roles and access

Admin, staff and viewer roles enforced in the database itself through row-level security, not just hidden in the interface. Staff run the day. Owners see the money.

  • Admin / staff / viewer
  • Row-level security

Illustrative interface · figures are examples

02 / In productionNIXE

Notademo.Aworkingoffice.

Regia was not designed in the abstract. It was built against a real hall, and changed by the people who use it every week.

A marriage hall in Tamil Nadu has been running its bookings, billing and accounts on Regia since 2026. Real dates, real money, real month-ends.

That is where the unglamorous parts came from: per-unit billing on the items that vary, advances set as a share of hall rent, an afternoon slot alongside the evening one, money fields that step in thousands rather than ones. None of it was on the first spec. All of it came back from the owner.

Status
Live at its first venue
Sector
Marriage halls, event venues
Region
Tamil Nadu, India
Stack
Vue 3, Supabase, Postgres
What changed
  • Bills that used to live in a notebook now close with the booking.
  • The margin on an event is visible before the next one is booked.
  • Staff enter the day's work. Owners see the month without asking.
03 / What's nextNIXE

Onehallprovedit.Nowitscales.

Regia is being taken from a system that runs one venue to a product that runs many.

01

White-label per venue

Each venue on its own isolated project with its own branding, provisioned from one canonical set of migrations. Physical separation, so a cross-venue data leak is not possible.

02

Native iOS and Android

The Capacitor shell is scaffolded. Push notifications for new bookings and advance reminders, biometric lock on resume, and a separately listed app per venue.

03

Self-serve onboarding

Venues provision themselves instead of being set up by hand, so Regia can take on halls faster than we can visit them.

04 / Request a demo

Seeitonyourowndates.

Tell us how your hall runs today and we will walk you through Regia against your own bookings and your own bill heads. No obligation, and no setup on your side.

Request a Demo