Your wealth.
Your data. Your server.

Because we sold you the software. Once. Forever. Not access to it.

The math at the founder price ($489): Kubera is roughly $340 CAD/year. Eighteen months in, you've already spent more than ManorMe. Five years in, you've spent over $1,700 — and you still don't own anything. With ManorMe, after the first payment, your cost is zero. The software lives on your infrastructure for as long as you want it.

The $489 founder pricing is for the first 250 households. After that, ManorMe goes to its regular price of $999, which is still a better long-term deal than any subscription — but it doesn't have the same urgency. If the math matters to you, this is the moment.

We charge a real number because the subscription model isn't free either — it just charges you forever, in pieces, while keeping your data on their servers.

Yes, absolutely. Let's be specific about what that means.

You'd spend roughly 80–150 hours of focused work over 1–2 months learning Next.js, Supabase, Row-Level Security policies, Postgres schema design, Stripe integration, the Canadian account taxonomy, and the dozens of edge cases that aren't obvious until you've built it once. You'd burn $200–500 in API credits on Claude or Cursor while you iterate. You'd land somewhere around 60–70% of ManorMe's polish and discover the missing 30% over the next six months.

ManorMe is the version of that build where someone else did the work, sweated the edge cases, and packaged it. $489 (founder pricing) for software that took thousands of hours to design, build, document, and harden is the trade. If your time is genuinely free and learning the stack is its own reward, building it yourself is rational. For most buyers, $489 is the lowest-cost way to skip ahead.

No. The full cost of being a ManorMe customer is:

• $489 once for the software (founder pricing, first 250 households — $999 after)
• One year of updates included
• After year one: optional $149/year for ongoing updates, or stay on the version you bought (free, forever)
• Optional 1-on-1 support beyond onboarding: $250/hour
• Optional white-glove install: $499 upfront

That's the entire picture. No premium tiers locked behind paywalls, no vendor rev share you haven't been told about, no upsells. The updates plan is genuinely optional — many customers will stay on the version they bought and never spend another dollar.

Subscriptions exist to keep customers paying forever. We chose not to do that — and we charge a real number once to make the business work.

The complete picture after the $489 founder price:

• Supabase hosting (your own account): typically free tier covers a single household. Heavier use, ~$25/month — paid to Supabase, not us.
• Vercel hosting (your own account): typically free tier. Heavier use, ~$20/month — paid to Vercel, not us.
• Optional voice AI via your own OpenAI key: roughly $1–10/month based on usage.
• Optional market data via Polygon or similar (your own key): $0–30/month.
• Optional ManorMe updates plan: $149/year.

Realistic 5-year cost of ownership for a typical household using the updates plan: about $1,085 CAD total at founder pricing. Kubera at $340/year over 5 years: about $1,700. You're saving over $600 across five years — and you own the software, on infrastructure you control.

Correct. After installation, we have no path back into your deployment.

Your Supabase project lives in your own account, billed to your own card. Your Vercel deployment lives in your own team, under your own login. We don't have a service account, a back door, or an admin panel. We can't see balances, beneficiaries, documents, or transactions.

This isn't a privacy policy commitment we could change tomorrow. It's how the architecture works. See the security overview →

Nothing changes for you.

Your ManorMe lives on your own Supabase and Vercel. We could shut down tomorrow and your deployment would keep running. Your data would stay in your database. The software you bought would keep working.

You wouldn't get future updates from us. But the version you bought continues to work as long as you want it to.

Honest answer: both are commodity infrastructure. We picked them because they're well-funded, proven, and replaceable.

Your Supabase database is standard Postgres — exportable to Neon, Render, AWS RDS, or a self-hosted server with a single command. Your Vercel deployment is a standard Next.js app — portable to Cloudflare Pages, Render, Fly.io, or AWS Amplify in an afternoon. If either vendor changed dramatically or disappeared, your data and your app survive. We document the migration paths in the customer portal.

Voice AI and market data work the same way — swappable across providers. ManorMe is built to assume its underlying providers are commodity, not lock-in.

Anytime. With no friction.

Your data lives in your own Supabase Postgres database — export to JSON, CSV, or SQL with a single command we document. Your uploaded documents live in your Supabase Storage — download them as a folder. Beneficiaries, executors, the family binder, account history all export to PDF.

If you stop using ManorMe entirely, you keep all your data. Delete your Supabase project and nothing remains anywhere, including with us. There is no lock-in by design — the same architecture that means we can't see your data also means we can't keep you.

Yes — that's what the one-hour onboarding call is for.

We don't expect you to know what Supabase is, what Vercel is, or what an environment variable is. On the call we screen-share and walk you through every click: creating the accounts, deploying ManorMe, setting up your domain, getting your first data in. By the end you have a working installation. If the call runs long, we don't stop.

If you'd rather we do the whole thing for you in advance: a full white-glove install add-on is available for $499.

A spreadsheet gets you about 30% of the way. ManorMe is the other 70%.

It calculates net worth with FX conversion automatically. It validates beneficiary percentages (sum to 100). It generates a printable Family Binder for executors. It manages document storage with encryption. It tracks contribution room across multiple accounts of the same type. It captures entries by voice. It supports household sharing with proper permissions. It logs every change for audit. It snapshots history daily for trend charts. It has an executor role with triggered access.

The spreadsheet version of this is doable the way running your own email server is doable. Most people are better off buying the polished version that someone else maintained for them.

You get all updates for the first year, included in your purchase.

After year one, you have two options: stay on the version you bought — free, forever — or join the optional updates plan for $149/year for ongoing releases and priority support. Either way, we never deactivate, downgrade, or remove features you already paid for.

Yes. A single ManorMe deployment supports multiple people in the same household — partner, view-only family members, your accountant, and an executor with triggered access.

Everyone logs into the same deployment with their own permissions. The household is the unit, not the individual.

Mobile apps that talk to a self-hosted backend are a support nightmare — and most of our customers' real use is on a laptop anyway.

ManorMe is built mobile-responsive, so you can use your deployment from your phone's browser. The dashboard, voice capture, and most features work well there. Native apps may come later — but only if we can build them in a way that respects the "your data lives only on your infrastructure" promise.

Yes. A full version of ManorMe with a sample Canadian household — accounts, mortgage, real estate, beneficiaries, executor, family binder — lives on our servers. You can click around every feature, see what's there, and decide if it's right for you. The demo is exactly the same software you'd be buying; the only difference is the sample data and that it runs on our infrastructure instead of yours.

Once you buy ManorMe, the software is yours and installs to your infrastructure. All sales are final at that point — but the demo is designed to be thorough enough that you won't need a refund policy.

Not openly, and we'd rather explain why than pretend otherwise. The code is the product. Publishing it openly would mean handing competitors a head start on cloning the work, and we can't sustain a $999 one-time business if anyone can rebuild it in a weekend.

What we offer instead, for sophisticated buyers who want technical verification before purchase:

• A complete security architecture overview document, free on request
• A signed-release attestation — every binary is cryptographically signed so you can verify the deployment running in your account matches the version we published
• An install transcript at deployment time — every command, every environment variable, every credential set, all visible to you in real time
• A network-traffic audit you can run yourself in your browser to confirm the app calls nothing outside your Supabase project
• Limited source review under NDA available for buyers who need it before deciding

See the full breakdown on the Security & Architecture page.