Paid signup: from purchase to first login

If you buy a paid StackJack plan on the stackjack.io marketing site, the purchase starts the signup. There is no separate registration form. StackJack first works out whether the purchase belongs to an existing organization; only a net-new business creates a new workspace and owner account.

Use your work email at checkout. For paid signup, StackJack treats one corporate email domain as one organization:

• If the exact customer or email already belongs to a workspace, the purchase is applied there.
• If one existing workspace uniquely owns the same corporate domain, the connector plans attach to that workspace. The buyer is not silently made its owner or added as a member, and the existing organization, owner, and billing identity are not replaced.
• If no workspace owns the corporate domain, StackJack creates a new workspace, identity organization, owner account, and the connector plans you bought.
• If the address uses a consumer or disposable email provider, the domain maps to more than one organization, or its organization is homed in another StackJack region, provisioning pauses for review. Payment has already happened: this path does not automatically issue or promise a refund, and it does not create a duplicate workspace.

Current pricing for every connector and tier is shown on the stackjack.io checkout and inside the portal.

The new-workspace journey, step by step

1. Choose and buy on stackjack.io. Pick the connector plans you want and complete checkout with your work email. The checkout collects your first and last name, company name, and email address — these become your StackJack account details only when a new workspace is created.
2. StackJack checks where the purchase belongs. Exact customer and email matches win first. Otherwise, a unique corporate-domain match attaches the plans to that existing organization. A new organization is created only when neither match exists and the business-domain checks pass.
3. Provisioning happens automatically for a net-new organization. Within moments of payment confirmation, StackJack creates:
   • Your workspace (tenant), named after your company.
   • Your identity account, with you as the account owner.
   • An active subscription for every connector plan you purchased.
4. Watch your inbox — up to three emails arrive:
   • StackJack welcome email — a short getting-started guide covering the whole first-run path: set your password, log in to the portal, connect your MSP tools, create AI credentials, and connect an AI assistant.
   • Password-setup email — sent by StackJack's identity service. It arrives as a password-reset message from a zitadel.cloud address; that is the expected sender. Use its link to set your portal password. One caution: the identity service's own console pages are not the StackJack Portal — after setting your password, always head to https://portal.stackjack.io.
   • Billing receipt from the payment processor — may or may not arrive depending on the processor's settings; it is informational only.
5. Set your password and sign in. Follow Your first sign-in — you will set a password, enroll in multi-factor authentication, and land in the portal.
6. You arrive in a ready workspace. Your purchased connector subscriptions are already active on the Connectors page. The first-login setup wizard then walks you through the two things only you can do:
   • Enter your own API credentials for each MSP tool (a plan activates the connector; your credentials make it work).
   • Connect your AI assistant to your MCP endpoint.

When the purchase attaches to an existing organization

The purchased connector plans become subscriptions on the existing workspace. StackJack does not create another tenant or identity organization, does not rename the workspace, does not replace its owner, and does not automatically add the purchaser as a member. Ask an existing Owner to invite you if you need portal access.

Because no new identity account is created, do not expect the new-workspace welcome and password-setup emails. The payment processor may still send its receipt.

If something goes wrong

• Purchase completed but no new account. First ask whether your company already uses StackJack. A corporate-domain match attaches the plans to that organization without creating a login for the buyer. Its Owner can invite you.
• Provisioning is waiting for review. Consumer or disposable email addresses, an ambiguous corporate domain, a workspace homed in another region, or incomplete checkout details can pause provisioning without creating anything. Do not buy again. Contact support@stackjack.io from the purchase email address and include the order or transaction reference if you have it. Support can attach the paid event to the correct tenant or route it to the owning region.
• A consumer-domain purchase was charged. The paid flow parks the purchase for review; it does not automatically refund it. Support must resolve the intended organization and the commercial outcome.
• New-workspace emails never arrived. First check spam for the two senders (StackJack and the zitadel.cloud identity service). The Forgot password option on the portal sign-in page can substitute for a lost password-setup email. If you still cannot get in, contact support@stackjack.io from your purchase email address. This advice does not apply to a domain-attached purchase, which creates no new login.

Already have a StackJack account?

If you already have a workspace, buy upgrades from inside the portal (Connectors or Billing) so the destination is explicit. A marketing-site purchase can match by the existing customer, exact email, or unique corporate domain, but a domain match does not grant the buyer access. If you purchased from a different address or your company has more than one StackJack organization, contact support instead of repeating checkout.