Beta
Early access
For first users and feedback
Pricing
Clear access paths, with no fake price promises.
The first release uses simple plan framing so users can choose the right access path without assuming a final public price.
Pro
Desktop plan
For active research workflows
Enterprise
Custom
For team and deployment talks
Plan framing
Start with access, not hard pricing.
Access
Beta
For early users who want to validate the workflow.
Popular
Pro
For solo traders and researchers who want a focused terminal.
Custom
Team / Enterprise
For desks that need shared rollout and deployment support.
What to expect
Keep the promise narrow and honest.
Risk
No profit claims
The product is a research terminal, not a guaranteed signal engine.
Data
Market access varies
Data coverage depends on source health, licensing, and market rules.
Process
Support path
Demo, download, beta access, and team conversations should each have a clear next step.
Access design
Plan boundaries should make adoption easier.
The pricing page should help users choose a path without pretending every deployment has the same data, support, and rollout needs.
Beta
Validate the workflow
Best for early users who want to test market coverage, watchlists, and desktop fit.
Pro
Daily research terminal
Best for active users who need consistent monitoring, news context, and review surfaces.
Team
Shared desk workflow
Best for small desks that need onboarding, repeatable processes, and internal alignment.
Enterprise
Deployment conversation
Best for compliance, data-source, integration, and support requirements that need planning.
FAQ
Questions that should not become support tickets.
Is the beta free?
The first access path can be positioned as beta access while the pricing model is finalized.
Will prices change later?
Yes. Plans can evolve as the release channel and support model mature.
Can I talk to sales first?
Yes. Team and enterprise paths should route into contact.
Choose an access path
Use pricing to guide the conversation, not to over-promise.
The page should help users understand the release structure before they ask for access.