Building a shared account layer that stays quiet until it becomes useful.
The tools should stand on their own. Login should appear only when it helps:
saving history, publishing under a stable handle, routing mail, or carrying
continuity across products.
Projects
A compact set of products with clear boundaries.
Account
One shared account system, but it should not dominate the homepage.
How login should feel
Browse and try tools before signing in.
Use the same email session everywhere once you do sign in.
Claim one handle and reuse it across public URLs and inbox routes.
Where login belongs
Inside each product, right at the moment continuity becomes useful.
Not as the homepage's main job.
Kept consistent by one shared auth system under the hood.