Choose how to sign in
Use a username and password, or a verified email or mobile sign-in method when delivery is available. Manage your identifiers in your account.
AuthManage your sign-in methods, profiles and permissions. Build sign-in into your own apps.
Open Auth ↗Shared service
Opens auth.heyinfi.com. No notebook content is passed with this link.
Your identity.
Your choice of profile.
Manage the way you sign in and the profile you use in participating HeyInfi apps. A work profile and a personal profile can belong to the same account without being the same identity to every app.
Choose who you are here
Create and select profiles for different contexts. The selected profile determines the identity an app receives, so switching profiles may show a different workspace or history.
Review each permission
See the requested profile and contact fields before continuing. Email or mobile identifiers are shared only when included in the approved grant. Your private notebook is not part of that grant.
Less repetition, clear boundariesA familiar sign-in.
A familiar sign-in.
Not blanket access.
Participating services can reuse a current Auth session and a remembered, unchanged consent. You may still be asked to choose a profile, approve new permissions or sign in again.
View and end Auth sessions in your account. Apps already open have their own sessions and may need a separate sign-out. During the domain transition, an older address and the new address can require separate sign-in.
Keep account changes deliberate
Account consolidation requires proof of control. A matching email address does not move or merge your notebook, conversations or other service records.
Never paste a password, sign-in code or client secret into another app or a support message.
Build on a shared identity layer.
Register an application, configure its exact callback addresses and use the documented OAuth interfaces. Keep each application's permissions and user-data boundaries explicit.
Application console
Manage app registrations, callback URLs and credentials through the developer console. App ownership belongs to the selected profile; it is not an ecosystem-wide administrator grant.
OAuth and profiles
Use authorization-code flow and PKCE where supported. Validate state, exchange codes server-side for confidential clients, and bind the resulting session to the chosen profile.
APIs and integration guidance
Explore the documented REST endpoints, SDK guidance, consent flow and app metrics. Check each interface's current contract before relying on it in production.
Security is a boundary,
not a slogan.
Passwords are hashed; browser sessions use HttpOnly cookies. OAuth access is bound to registered callbacks and approved scopes. Cookies are not shared across every HeyInfi subdomain.
What this does not promise
Auth does not automatically grant access to notebooks, workspaces, payments or AI spending. Availability of email/mobile delivery and each app's integration must be checked separately. No certification, universal SSO or all-app sign-out guarantee is implied.
Nearby in HeyInfi.
PlatformCore product
Business
Create projects, save versioned drafts and review work in private or team workspaces.
Workspace/developer preview; cross-service automation and paid execution remain pending.
Explore BusinessPlatformEarly access
Tools
Keep a record of tools and estimated usage.
Manual estimates, not provider billing or enforced spending limits.
Explore ToolsPlatformEarly access
App Builder
Organise app registrations, versions and readiness checklists.
Checklists are self-reported, not automated deployment or certification.
Explore App BuilderHeyInfi brings the Infi family together. During the transition, working apps still open at their existing addresses and may show their earlier names. Your existing data stays where it is.