Checks before commits, on the server.
On a 506(b) raise, the software prevents a commitment from being recorded until the operator marks their own relationship and suitability checks complete. Mownt tracks Form D filings and writes key steps to an append-only audit log. SOC 2 Type II is in progress.
Server-side checks, with key steps logged.
Each of the four pillars below runs on the server. A misconfigured browser, a forwarded link, or a copy-paste of a private deal URL cannot bypass them.
On a 506(b) raise, the software prevents a commitment from being recorded until the operator marks their own relationship and suitability checks complete. The checks run on the server, and there is no client-side toggle that can bypass them. Until the operator marks an investor's checks complete, a private 506(b) deal page shows them only the deal name.
Record each investor's accredited status with their suitability answers. Mownt shows a running count of non-accredited investors on each deal. Your overall count, across offerings, is yours to confirm with your attorney.
The 15-day Form D countdown starts when the first soft commit converts to a sale. The deadline is shown on the operator dashboard and on the deal page header until the filing is logged. Amendments and annual updates surface the same way.
Key steps, such as accepting an investor, clearing a relationship check and logging an interaction, are written to an append-only, hash-chained audit log keyed to the investor and the deal. Entries cannot be edited after the fact.
In progress.
Server-side 506(b) commit checks are our concrete differentiator today. SOC 2 Type II lets enterprise procurement check the box.
We will publish the Type II report once issued. Until then, operators with procurement requirements can request the current control matrix and the Type I bridge letter when available.
Your data, your tenancy, your export.
Operators own their pipeline, their soft-commit history, their audit log, and the documents their investors upload. We treat data export as a first-class workflow, not a friction point on cancellation.
Operator and investor data live in a US-region Postgres database with row-level security. Every query that crosses the operator boundary is filtered by the authenticated user's operator_id on the server.
Deal access is granted explicitly per investor by the operator. Until the operator marks an investor's relationship checks complete, a private 506(b) deal page shows them only the deal name. Investor portal sessions are scoped to the investor's own deals, no cross-tenant data leakage.
PDFs and KYC uploads sit behind Supabase storage with operator-scoped policies. Investor uploads (drivers license, accreditation letter) are isolated per investor and per operator. No public URL paths.
Export contacts, investors, interactions and cap tables as CSV, and investor dossiers as CSV or PDF. Cancellation does not lock your data.
No security claim hidden behind a higher tier.
The six items below are the same on every plan, from Launch Mode through Pro. The 506(b) commit checks are not an add-on.
Apply for early access, we’ll send the full controls breakdown.
Tell us a bit about your raise and your procurement requirements. We’ll send the tier that fits and the current control matrix together.