Why MyBloodlines Has No Groups, Only People

Most software that lets people share anything is built out of groups: a workspace, a family account, a tree that somebody owns and invites others into. MyBloodlines has none of that. There is no “family group,” no account that contains a set of relatives, no owner who holds the tree. There are only two things: people, and the parent-child relationships between them. Everything else — including privacy, collaboration, and how the whole thing grows — is built on top of those two ingredients and nothing more.

This sounds like a small technical detail. It’s actually the design decision that makes MyBloodlines behave differently from every family-tree app built around a shared account or a single global tree.

No container, just a graph

In MyBloodlines, when you record your parents, your grandparents, and your children, you’re not filling in “your family group.” You’re adding people to one continuous graph of individuals and relationships. Nobody owns that graph. It isn’t partitioned into families. There’s no membership list, and no boundary drawn around a set of people that says “this group is one family and that group is another.”

Anyone can start recording — the moment you create your own profile with no existing relatives, you’ve begun. From there the record expands indefinitely as relatives are added outward in every direction, and two families who had no link between them become connected the moment someone records a real relationship across, most often a shared child. Because nothing is boxed into a container, there’s no limit on how far it can grow and no seam to stitch when two sides join: one new parent-child link is the entire join.

Privacy without groups: the permission boundary

The obvious question is: if there are no groups drawing the lines, what keeps anything private? The answer is the other half of the design — the permission boundary. Instead of privacy being a property of a group (“members of this family can see this family’s tree”), it’s computed individually for every single person, from where they sit in the graph.

Your permission boundary is everyone you share a common ancestor with, plus the other-side parents of those people. That’s it. It’s calculated fresh for you, and calculated differently for everyone else, because everyone sits somewhere different. Two relatives standing one link apart have overlapping but not identical boundaries. There’s no group setting to configure, because there’s no group. The full rule, with worked examples, is in permission boundaries in MyBloodlines.

This is the combination that no group-based app has: no groupings, plus a per-person permission boundary. Together they let the graph stay completely private while still being one shared, connectable structure rather than a pile of walled-off family accounts.

Why this specific design unlocks so much

Once you remove groups and compute access per person, a series of things that are normally hard become automatic.

It expands indefinitely. Nothing caps the record at “one family,” because there’s no family object to cap. Relatives keep being added outward as far as anyone knows them.
Connecting two sides is easy. Linking two families who weren’t connected before is just recording one real relationship between a person on each side. No merging of accounts, no reconciling two group memberships — see how to add a child when parents are from different bloodlines.
It has genuinely shared history. Because there’s one canonical copy of each person rather than a copy inside each family’s group, a story or photo recorded once is visible to everyone whose boundary includes the people in it — no duplication, no conflicting versions. How that works day to day is in one shared family history: how relatives record together.
Its upkeep is decentralized. No single owner is responsible for the whole graph. Each person maintains their own part, within their own boundary, and the graph as a whole survives any one person losing interest.
It passes smoothly to the next generation. Because access follows the graph rather than a login someone has to hand over, the next generation simply claims their own profiles and inherits access to their part automatically, forever.

A concrete example: you, your spouse, your children

The cleanest illustration is a married couple. You have access to your side of the graph — your ancestors and relatives. Your spouse has access to a different part — his or her side. Neither of you automatically sees the other’s ancestors, because you don’t share a common ancestor with your in-laws.

Now record your child. Your child shares a common ancestor with you (you) and with your spouse (your spouse), so your child’s permission boundary naturally includes both sides. Nobody configured that. No group was created and no one was added to it. It falls straight out of the graph: the child sits at the point where two lines meet, so the child can see down both of them. Your children have access to both sides by design, purely because of where they are in the graph — and their children will, in turn, see even further. If you want to see your spouse’s side too, that’s a deliberate, separate grant of read-only view access, not something a group membership would have handed you.

That is the whole idea in one picture: no groups, only people and relationships, with access that follows the shape of the family itself.

Start recording your bloodline Claim your profile and begin at MyBloodlines →