Create your account and choose a sign-in method

The customer portal supports several sign-in methods, so you are not limited to email and password. Your portal account owns billing, services, and support access. Automation keys and service credentials are separate and should be managed separately.

Before you start

• Decide which account should own billing, services, and support for your business or team.
• Choose one primary sign-in method first.
• Add stronger login options after your first successful sign-in.
• Do not use API keys or service passwords as a replacement for portal login.

Recommended order

1. create or claim the main customer account for the business
2. complete email verification or finish the chosen OAuth or passkey signup flow
3. land in the portal and confirm the profile and billing identity
4. add stronger login protection such as TOTP or passkeys
5. create API keys separately only if you need automation

Supported signup and sign-in paths

• Sign up with email and complete the verification step that follows.
• Continue with Google when that provider flow is available.
• Continue with GitHub when that provider flow is available.
• Use passkeys on supported devices for passwordless account creation or sign-in.

What happens during email signup

When you register with email, the platform creates the customer identity and starts a verification step. That matters because the same account later owns invoices, wallet balance, services, settings, support context, and optional API access.

In practice, the flow looks like this:

1. Enter your email address and accept the terms shown in the signup form.
2. Complete the verification code step sent to your email.
3. Finish the first sign-in and land in the customer portal.
4. Add profile and billing details before placing production orders.

If the email is already taken, the platform does not create a duplicate account. Instead, it points you back to sign in.

OAuth and passkeys

Google and GitHub OAuth are supported sign-in paths. They are useful when the team already manages access through those providers and wants less password handling.

Passkeys are also part of the customer login experience. On compatible devices they provide a passwordless option that is faster to use and more resistant to phishing than a password-only flow.

What this account is for

Your portal account is the identity used for billing, services, and support. It is used for things like:

• viewing and paying invoices
• managing profile and billing details
• tracking services and service status
• using referral features
• configuring login security such as password, TOTP, passkeys, and linked OAuth accounts

It is not the same thing as an API key, and it should not be confused with any service-specific credential you may receive later for a provisioned product.