Create Account

Start the onboarding path from a dedicated page

Every `Create an account` button now lands on its own internal page instead of sharing a generic access section. This keeps onboarding clearer and easier to replace later with a real signup form.

Choose a plan Talk to the team

Step 1

Define your main use case

Choose whether your first deployment is mainly about wallet screening, customer onboarding, monitoring, or investigations.

Explore workflows

Step 2

Select the rollout scope

Use the pricing page to align the account setup with manual reviews, repeatable monitoring, or a more integrated operating model.

Review plans

Step 3

Prepare support and trust routes

Decide how your team will handle verification, contact ownership, and case escalations before the account goes live.

Set verification paths

Step 4

Move into activation

Once the structure is clear, this page can later be swapped out for a real registration form or workspace setup flow.

Already have access? Log in

Account setup

What a good signup page should clarify

Before a backend exists, the most useful thing this page can do is orient the user and prevent the next step from feeling fake.

What they are signing up for

Make the product scope obvious so the account path matches the real use case.

What happens next

Point clearly to pricing, support, and contact instead of sending users into dead ends.

How to recover if they are already a client

Keep the login route close by so existing customers do not get trapped in the signup flow.