Jump to the product you care about, or start with how the platform fits together.
How the Britemet products relate.
Britemet builds operational software that turns scattered records (people, properties, vendors, documents, schedules, and approvals) into one secure system. Two products share that discipline at different scales: Home for households, and Estate for Private Offices.
Home is for a household you live in. Estate is for Private Offices running residences, staff, and discretion-sensitive operations. Not sure? Contact us and we will help you choose.
Home is self-serve at home.britemet.com. Estate is provisioned by arrangement with separate onboarding. They share platform ideas (records, roles, security) but are not the same consumer signup flow.
Households, families, and everyday home operations.
The operating system for a household: maintenance, warranties, inventory, documents, vendors, family calendar, emergency info, and more, shared with the right people under clear roles.
3 months free, then $49.99/year per household (about $4.17/month billed annually). No card required to start. Unlimited household members on the plan.
The owner invites partners, kids, and sitters with roles. Children see shared day-to-day context without finances or codes. Sitters get a limited, expiring view when you share it.
Brit is the built-in assistant for Britemet Home. It answers from your household records and can help create reminders and tasks, without pulling encrypted vault secrets into chat context.
Yes. Export is a first-class goal, and Home is designed so you can cancel when you no longer need the plan. Account controls live in-product after signup.
Use in-app Help & Support after you sign in, or email hello@britemet.com / contact form.
Private Offices, Principals, Chiefs of Staff, and multi-residence operations.
A Private Office command center for residences, staff, vendors, visitors and access, travel, Principal intelligence, documents and SOPs, incidents, approvals, Thread tasks, Status Net, onboarding and handover, continuity, and encrypted messaging on web, iPhone, and Android: the operating scope a Chief of Staff runs, in one discreet system with seventeen role types.
Principals, Family Offices, Chiefs of Staff, Estate Managers, Directors of Residences and Security, Executive Assistants, Personal Assistants, house and service staff, Executive Protection, and scoped contractors or vendor contacts. The product defines seventeen least-privilege roles so each seat gets the view it needs. See the full list on the Estate user types section.
No. Home is built for one household with family roles. Estate is built for private-office scale: multi-residence context, staff/vendor governance, access and guest control, incidents, executive-ready reporting, and encrypted messaging on iPhone and Android for the Private Office.
Yes. Estate includes secure messaging for Private Office coordination on iPhone and Android, with encryption in transit and at rest and membership and role controls so channels stay inside the office. It is built so sensitive operational talk does not have to live in personal SMS or consumer chat apps. Details are covered in an Estate briefing.
Typically no. Estate is offered by arrangement with onboarding tailored to the office. Request a briefing or use the contact form and select Britemet Estate.
Effective access is the intersection of role capabilities, estate scope (which residences), and clearance (how sensitive the data is). Seventeen roles map to server-enforced capabilities. Org-wide leadership sees all estates; everyone else needs an ACTIVE estate grant. Clearance bands gate Principal intelligence, vetting detail, and other high-sensitivity fields. Sensitive fields remain encrypted; important actions are attributed. Details: access model.
Yes. Multi-residence operating knowledge is a core Estate use case: shared vendors, staff, protocols, and continuity across properties the office manages.
Estate is scoped for operational events (incidents, guest/access decisions, approvals) so informal chat threads are not the only system of record when stakes are high.
Use Request an Estate briefing. Share operating scope (residences, staff size, current tools). We will follow up by email to schedule a focused discussion.
Mechanisms shared across the platform; Estate adds the full private-office data-layer control set.
Sensitive fields use AES-256-GCM envelope encryption with controlled reveal. Ciphertext can be bound to tenant, record, and field. TLS protects data in transit; databases and files use encryption at rest with managed keys. See the full Security page.
Non-negotiable rules (force-audit on mutations, least-privileged app role, dual-control gates, legal hold, classification floors, tenant consistency) are enforced in the data layer so a buggy or incomplete application path cannot simply skip them. Details live on the Estate security posture section and the Security overview.
Break-glass and privileged overrides require dual approval, a distinct executor, time bounds, and single-use consumption. Control-plane evidence is not writable by the normal application role.
Uploads are scanned (malware / DLP). Blocked or infected verdicts cannot be silently marked clean. Downloads stream through an authenticated proxy that re-checks grant and scan state and records attributed access.
Security overview · Privacy Policy · Terms of Service · AI Policy · Estate posture · Contact
Brit is optional. Owners and admins can turn AI off for the whole household in Settings → AI & privacy (or email privacy@britemet.com). Production uses Claude on AWS Bedrock under our account. Vault data (Wi‑Fi, codes, medical) stays in your database and is designed never to go to a model. Maintenance, vendors, and inventory may be included only when AI is on and your role allows. Free-text you type in chat can go to the model; the product warns you not to paste secrets. Full detail: AI Policy and Privacy Policy.
Start Home free, or request an Estate briefing. We will meet you where you are.