Everything the storefront stands on

There is a screen in our product that lists every key, fob and gate card ever issued in a community.

Nobody has ever bought a gate card.

We built it anyway, because when the sync runs, all of it lands. And almost everything the platform generates later reads from it.

The admin side has two altitudes: company, and association.

At association level the hub splits three ways.

Community → units, owners, board members, vendors, common areas, passes and keys.

Compliance → violations, architectural requests, work orders, delinquencies, and the CC&R library.

Financials → invoices, cost centers, transaction accounts, chart of accounts, insurance.

Plus a dashboard for every community: revenue, packages sold, refunds, unit and owner and board counts, recent orders, and whatever is currently waiting on a human.

Now the part that matters.

This is not a second product bolted onto the side of the storefront.

It's the source.

Every merge token in a letter. Every pre-filled field on a form. Every branch in a flow. Every live table that prints a community's open violations at the second it generates.

All of it reads from here.

Otherwise somebody is reading it off a sticky note. Onto a legally binding document.

Two more things.

When a new association turns up in a sync, it doesn't arrive as a row. It arrives with its own sellable packages already created.

Onboarding a community stops being a data-entry project.

And the knowledge base is live: violation types, architectural categories, notes across eight kinds of record, pulled straight from the accounting system.

So when a manager needs to know what a violation category actually covers, the answer is on the screen they are already looking at.

The storefront is the visible ten percent.

This is the other ninety, quietly holding it up.

Next: the money — who takes the payment, who keeps it, and who earns a cut without ever holding it.