Existing users
Authenticate through device presence
Users can choose Aegir at sign-in and let the platform route them to desktop, mobile, QR, or later extension-based trust completion.
Free security product for users
Aegir gives users a free, device-backed identity layer they can carry across Aegir-enabled and federated systems.
Start with a free Aegir account, install the trusted desktop or mobile app, and keep your security in your own hands. Aegir is designed to minimize tracking, encrypt sensitive profile data, and let you decide what personal information is shared when you sign in across supported systems.
New users
Start with a free product
New users move through a real onboarding path that explains why Aegir is free, why the trusted app is required, and how encrypted profile data is handled.
Compliance path
KYC is visible now, deeper checks later
KYC is present in Beta-1 as a workflow stub, while camera integrity checks and Foxlin.Research-backed review logic follow in the next slices.
Why users adopt Aegir
The user product is free and centered on trust, privacy, and continuity.
- Authenticate with strong device-backed trust instead of relying only on passwords.
- Use Aegir as the security layer beneath the federated identities you already trust.
- Keep sensitive profile data encrypted and share personal details only when you choose.
- Preserve continuity across providers, devices, and future recovery events with minimal tracking.
Existing user flow
Authentication starts with Aegir presence, then resolves through the best trusted path.
- Desktop handoff to the Aegir security app when the local app is installed.
- Mobile push approval when a trusted phone app is available.
- QR launch into the Aegir phone app when desktop-to-mobile handoff is needed.
- Browser extension support remains a later Beta-2 expansion.
Once presence is confirmed and the user proves local control, Aegir can let them choose the federated identity they want to use for that login event.
Signup path
New users should be able to move from explanation to enrollment without guessing what comes next.
- The public landing page should explain the value of Aegir before asking the user to commit.
- Signup should make the trusted desktop-or-mobile app requirement explicit.
- The user should understand that their sensitive identity data is intended to stay encrypted and selectively shareable.
- The path should flow naturally into secure-app installation and encrypted-profile onboarding.
New user onboarding
Users learn the trust model first, then create an encrypted profile and install their secure app path.
- Read why Aegir improves privacy, security, and recovery while remaining free for users.
- Sign up and create your base encrypted Aegir profile.
- Install the Aegir desktop or mobile app and use a secure local factor like Windows Hello, Face ID, fingerprint, or device PIN.
- Optionally link other logins later so Aegir can protect them without forcing broad personal-data sharing.
KYC and research path
Beta-1 uses a test KYC page today while the stronger verification stack is still being built.
- Beta-1 includes a visible KYC workflow and a pass-through test page for flow validation.
- Production KYC will run through the Aegir app and reject virtualized cameras.
- Foxlin.Research will later support email and social-presence correlation for manual review decisions.
- Manual review remains part of the future compliance and admin workflow.
Security promise
Aegir is designed to give users maximum security with the minimum practical tracking.
- The user's security posture should be anchored to their trusted app and local secure unlock, not just a password field.
- Aegir should log only what is needed for trust evidence, compliance, and abuse prevention.
- Sensitive profile details should stay encrypted and user-controlled wherever possible.
- Age, consent, and stronger identity proofing should layer on top of the trust core without broadening routine tracking.
Developer platform
Developer and package pathways remain visible, but the user product now has its own clearer entry point.
- Starter: 1 app, 2 environments, package onboarding, and email support.
- Growth: multiple apps, team key rotation, richer audit visibility, and ACH-capable billing.
- Enterprise: dedicated environments, federation rollout planning, and deeper operational support.
Packages and delivery
NuGet and NPM are the active Phase 1 package surfaces.
- NuGet package for .NET applications embedding Aegir trust flows.
- NPM package path for JavaScript and TypeScript applications.
- Java packaging path through Maven Central for JVM consumers.
- Operational distributions for desktop and CLI delivery through channels like Chocolatey, WinGet, and Homebrew.
Developer billing paths and package distribution remain visible here while the end-user trust experience becomes clearer on the user side.