Why we built one account for every DataBoss app

Every DataBoss app — Personal Assistant, Corporate Assistant, Lyrics, Translator, POS — started as its own project, sometimes in its own language, on its own server. The one thing we didn't want to rebuild for every app was sign-in.

So we split the problem in two: identity is shared, everything else isn't. One Data Robot Technologies account gets you into any DataBoss app. What that account can actually do inside each app — its plan, its data, its history — stays entirely with that app.

Where the line sits

Paying for DataBoss Lyrics never unlocks DataBoss Translator. Each app checks its own entitlement record for your account, scoped to that app and nothing else. The shared identity service knows who you are; it has no opinion on what you've paid for anywhere except through that per-app record.

Shared identity, independent everything else — that's the whole rule.

Why this held up as the suite grew

New apps join the suite regularly, often built by different people in different stacks. Because the boundary is so narrow — one identity service, one token format — a new app only has to integrate with one thing to get sign-in for free, without inheriting any of the older apps' technical decisions.