Getting started
Create an account, complete onboarding, and find your way around the tools in the app.
Signing in
The sign-in screen offers three routes into the product: continue with Google, connect a crypto wallet (the modal handles connection and message signing), or use email and password. The email path is two-step — you enter your address first, the app checks whether an account already exists, and then asks a new user for a name and password, or an existing user for their password only. A “Forgot password?” flow sends a reset link. The same screen also serves the Partners creator program, which is invite-only and expects the email you were invited with.
Confirming your email address
Accounts created with email and password are not usable immediately. After you submit the sign-up form, a “Check your email” screen names the address the verification link went to. The same screen appears if you try to sign in with an account that has not been verified yet. It carries a “Resend email” button behind a countdown, and a link back to the sign-in form. Once verification succeeds you continue into onboarding.
What onboarding asks you
The first screen after sign-in depends on your plan. Without a paid subscription you land in the domain wizard — “Pick your free domain” — where you choose one domain; the page notes you can change it later in settings. Paid plans use the same wizard to confirm the domains covered for the current billing period. Full-access accounts skip the picker and are onboarded automatically. Accounts on a trial first answer one optional question about where you heard about Athenum, with a Skip option; answering or skipping both count, so you are not asked again.
What a domain is
A domain is a named slice of the product catalog, and there are exactly five of them: Order Flow & Market Depth, Derivatives Intelligence, Macro & Data, Macro Intelligence, and Traditional Finance. Each one owns a fixed set of features, and every feature belongs to exactly one domain — the catalog is a partition, not a set of overlapping bundles. Order Flow carries seven features, Derivatives ten, Macro & Data eight, Macro Intelligence seven, and Traditional Finance six, thirty-eight in total. The same catalog is what the onboarding cards show you, what your account stores after you choose, and what the app consults before it opens a page.
The five domains sit in two groups. Order Flow and Derivatives form the lite group; Macro & Data, Macro Intelligence and Traditional Finance form the pro group. That grouping is what plan rules are written against: some plans may pick only from the lite group, and the plans that reach the pro group cap how many pro-group domains you may hold at the same time. Whatever you end up holding is stored as an active-domain list on your account and read on every request. It is one half of the access decision; your plan tier is the other.
Plan tier and domain are two different axes
Access is decided by two independent facts. The first is your plan tier: four of them, ranked, from the unpaid tier through Lite and Pro to Pro+. The second is the set of domains attached to your account. The tier decides how many domains you may hold and how deep the feature list runs inside each one; the domain decides which subject areas you hold at all. The unpaid tier and Lite both hold exactly one domain from the lite group, and both see only the headline subset of that domain's features. Pro holds three domains with at most one from the pro group. Pro+ holds all five and sees every feature.
Because the axes are independent, a higher tier does not by itself open a page, and the right domain does not help when a page is gated on a tier capability instead of a domain. The selection rule is exact rather than a maximum: a plan that grants three domains rejects a submission of two or of four, and duplicates are rejected as well. Pro+ is the exception that never picks — its selection is filled in on the server at first login, which is why full-access accounts never see the picker at all.
| Plan | Domains held | From the pro group | Feature depth |
|---|---|---|---|
| Free | exactly 1 | 0 | headline subset |
| Lite | exactly 1 | 0 | headline subset |
| Pro | exactly 3 | at most 1 | full catalog |
| Pro+ | all 5, assigned | 3 | full catalog |
Changing your domain selection later
A paid selection is locked for the remainder of the billing period. The lock date is computed when the selection is written: on a monthly plan it runs to the next billing anniversary, walking forward month by month so the date always lands in the future; on a yearly plan it runs to the first of the next calendar month in UTC, and each subsequent change re-locks to the first of the month after that. On a yearly plan the change window is that first of the month itself — a request made on any other day is refused with the same conflict. The reconfigure screen reports whether the lock is still in force, and an attempt made too early is refused with a conflict rather than quietly applied. The page action and the API path enforce the identical rule.
The reconfigure surfaces are built for subscriptions. Opening the reconfigure page without an active subscription redirects to the home page, and the equivalent API call answers with a plain error instead. Free selections work on different machinery: no subscription, no billing period, no lock window, and a fresh submission simply replaces the previous choice. Re-submitting the same set is treated as a replay — the stored state and its version come back unchanged instead of a second record being written.
When the first-login check does nothing
The onboarding decision runs on nearly every signed-in page request, not only the first one, and it deliberately skips a list of paths so it can never trap you: the onboarding pages themselves, the sign-in screen, billing, the upgrade page, the subscription part of settings, API routes and application assets. That exclusion list is why the upgrade page stays reachable from a locked page instead of bouncing you back into the wizard, and why a form error on the attribution step can re-render in place rather than looping through a redirect.
Two outcomes the rule can produce cause no redirect at all. A past-due subscription, and a subscription whose billing period has not been reported yet, are both classified as blocked states, and the request handler has no branch that acts on them — those accounts continue to the page they asked for and are limited only by the normal access gate. The whole block also fails open: if the evaluation throws, the failure is logged and the request proceeds without a redirect rather than returning an error page.
Where things are after you sign in
Onboarding ends on a welcome page and from there on the dashboard. Each tool then has its own page — Terminal, Chart, Orderbook, Futures, Liquidations, Liquidation Heatmap, Funding Heatmap, Volume Delta, Range Analysis, Correlation Matrix, Options, ETF Charts, World Map, Macro, TradeFI and Prediction Markets. Account pages sit alongside them: Settings, Upgrade, Referrals and Support. Which of these you can open depends on your plan and on the domains you selected during onboarding.
Two exceptions worth knowing, so you do not mistake them for a plan problem. CME Detector is switched off for every account at the moment and answers “coming soon” regardless of your subscription. Prediction Markets has a page you may be able to open, but the tutorial still lists it as in development, so treat what you see there as unfinished.
What happens when you open a page you do not have
Every request passes one gate that looks the path up in a routing table and produces one of a few answers: no rule at all, platform, sign-in required, a tier capability, or a domain. If you are signed out and the page is not on the public list, you get a 303 to the sign-in screen with your original path preserved in a redirect parameter, so you land where you meant to go once you are in. If you are signed in but the required domain is not in your active list, a page request answers with a 303 to the upgrade page, carrying both the path you tried and the tier that would cover it.
API calls are answered differently. Instead of a redirect they return HTTP 402 with a machine-readable body naming the feature key, the tier required, and — for domain gates — the domain you are missing. A signed-out API call returns 401. A third answer, 403, appears only when the rule itself cannot be resolved; its body carries an opaque code and the underlying reason stays in server logs. What the gate never does is pretend the page is missing: a page you have not paid for is a redirect or a 402, not a 404.
Before you click, the interface usually says so. Navigation entries and cards leading into a domain you do not hold are wrapped in a lock overlay: the link underneath is made inert, a badge carries the tier label, and activating the surface opens the paywall dialog instead of navigating. The overlay is a real button, so keyboard focus stops there rather than slipping through to the link behind it. Until your entitlements have loaded the gate renders as pending rather than guessing, so paid accounts do not see a lock flash before the page settles.
What is live today
The feature tutorial is the current inventory: it marks fifteen features as live — Trading Terminal, Orderbook, Advanced Chart, Options Max Pain, ETF Flows, Funding Rate Heatmap, Liquidations, Liquidation Heatmap, Range Analysis, Volume Delta, World Map Intelligence, Futures Overview, Macro Terminal, Correlation Matrix and TradeFI Terminal — and lists six as still in development: Sentiment Analysis, Prediction Markets, On-Chain Analytics, Wyckoff Analysis, Institutional Quant Engine and Locked-In Range Analysis. Each live entry in the tutorial carries an overview, usage notes and tips.
What you can change in Settings
Settings is a single page with seven sections in a sidebar: General, Account, Language, Preferences, Alerts, Data & Privacy and About. Each section is addressable by URL fragment, so a link ending in a section name opens straight to it, and switching sections rewrites the fragment without a reload. General holds your display name and your handle. Account shows the email on file with a verified or unverified badge, your membership and what it includes, a partner-code field, saved payment methods, billing history, an entry point for changing membership, and connected wallets.
Language lists the display languages and switches by loading the localized form of the page you are on. Preferences splits into trading defaults — a default symbol and a default timeframe — and display options for number format and timezone. Alerts is not configurable yet: the section renders a "Coming Soon" panel that names desktop push and email digests among the planned channels. Data & Privacy offers two actions on locally stored preferences, clearing them and exporting them as JSON, plus an account deletion control that takes two steps — but the second click currently only produces a notice that account deletion is not available yet and that you should contact support.
Keyboard shortcuts and the command palette
Command-K, or Control-K, opens a command palette. It is wired separately on the home page, the orderbook shell, the Macro section and the TradeFI section, so the same keystroke reaches a palette scoped to wherever you are. Inside the palette, arrow keys move the selection and Escape closes it. In TradeFI, Escape closes overlays in a fixed order — palette first, then the shortcuts sheet, then alerts and portfolio — and the question-mark key toggles a shortcuts reference. Macro binds question mark the same way. Single-key shortcuts are suppressed while the focus is in a text field.
Both large sections also navigate by number. In TradeFI, keys 1 through 9 and 0 jump to the ten tabs, from Overview through Bonds. In Macro, 1 through 9 jump to the first nine sections and 0 selects the tenth; the square-bracket keys step between sub-tabs, H returns to the Macro home, R forces a data refresh, and the period key opens the data-health page. Macro additionally binds Command-E to print and Command-Shift-F to expand the focused chart, and deliberately leaves Command-R to the browser.
Sessions, signing out, and languages
A session lasts thirty days and is refreshed at most once a day as you keep using the app; a five-minute server-side cookie cache keeps repeat requests from re-reading the session record each time. Signing out is available from the profile menu and from the command palette, and the profile menu disconnects a linked wallet in the same action so a wallet user is not left half signed in. Accounts can be linked across the password, wallet and Google methods, which is why the same person arriving by a different route reaches the same account rather than a second one.
The app ships display languages for English, Turkish, Hindi, Korean, Russian and Chinese; picking one in Settings navigates to the localized form of the current page. Accounts created with email and password cannot sign in until the address is verified, and passwords must be between eight and one hundred twenty-eight characters. The Google route always presents the account picker rather than silently reusing whichever Google account the browser already holds, which matters on a shared machine.
Next steps
- Whale walls — reading large resting orders in the live book.
- Liquidation heatmaps — the estimated surface and the realized feed.
- Billing & subscriptions — tiers, checkout and trials.