Many niche apps.
Single shared graph.
Converging into the super-neat-app.

🎯 “25 products? That's unfocused.”

It would be — if each product were built from scratch. They aren't. Every Sneat app is an extension of the same platform: one instance, one authentication system, shared modules for members, contacts, calendar and budgeting, with data separated at the space level. A family space and an engineering-team space run the same code.

Product count isn't scattered attention; it's the output of a build-once, reuse-everywhere machine. Each niche app is a cheap experiment in distribution — and whichever ones win, they all feed the same graph. Today every extension is ours; the platform is built to eventually open to third-party developers.

🚪 Consumer first, with a work door in reserve

sneat.app — everyday personal life for families, friends, groups and communities — is where our focus and roadmap sit today. That's where the graph compounds and where near-term revenue lives. Its public front door — the family story, positioning and discovery site — is sneat.family.

The same platform has two team-facing doors on identical machinery: sneat.team — team rituals (sprints & retros, standups, mood pulse) for any small team, live with a waitlist today — and sneat.work — software delivery from idea to release, a deliberate long-term option we keep in reserve so the consumer graph can compound first.

🧱 One platform, any vertical

Every product here is the same move: take the shared primitives — spaces & teams, contacts, calendar, locations, documents, assets and money — add a thin domain extension, and ship a vertical app. The hard parts are already built and battle-tested across the portfolio, so a new vertical is weeks, not years.

That makes Sneat a framework, not just a family of apps. School-Portal.app is the pattern for education, hospitality has its own pack, and the same primitives extend to work verticals down the line. The moat isn't any single app — it's the platform that makes the next one cheap to build, and it's built to be open to third-party developers.

We've made this a first-class concept: a Vertical is a curated, versioned pack of extensions applied when a Space is created — so a new industry is an authoring task over a stable extension graph, not an engineering build. See how Verticals work →

🧲 The growth engine that pays us for every user it delivers

Consumer apps aren't the only way in. In development is a layer of focused CRM apps for businesses whose customers are families — a distribution channel with negative CAC. Most consumer startups pay to acquire each user; here the business pays us for the software and hands its customers into our graph. Acquisition flips from a cost line to a revenue line.

Two-sided compounding — the graph makes the B2B product frictionless, and the B2B product delivers users at negative cost. Customer acquisition, inverted.

We target two archetypes on purpose:

• High-throughput — PreCheckIn.app (hospitality): QR/link-based pre-arrival check-in and guest registration for hotels, resorts, holiday parks and serviced apartments. Every arriving guest is asked to provide identity and travel information before arrival, often including passports, family members, vehicles and emergency contacts. The property’s need is transient; the verified family/travel graph it contributes to Sneat is permanent. The same Hospitality vertical naturally cross-sells Kids-Club.app for resorts with children’s activities — reusing the same parent-child graph, allergies, consent forms and authorised-pickup data while adding session booking, capacity limits and paid activities.
• High-retention — the same families return term after term. Sneat Sports (sport clubs, via GameBoard.live) bridges the club graph (club → team → player → coach) with the family graph; School-Portal.app (a whole-school tenant for language, music & tutoring centres — students, classes, timetables, attendance, fees) does the same for schools. Recurring enrollment becomes durable engagement.

🔓 Open source, on purpose

We open-source the foundations the graph is built on — not despite the moat, but because of it. When you ask people to trust you with the data of their everyday lives, the infrastructure that holds it can’t be a black box. Open code earns that trust, invites developers in, and gets battle-tested in the open. The moat was never the plumbing — it’s the graph, the apps and the network that compound on top of it, and that’s exactly where we capture value.

Open where it builds trust and community; proprietary where the compounding value lives. That’s the discipline — we know exactly which is which. See everything we’ve opened →