First-run guide
Pick the path closest to you
How this site is organized
Everything below is static marketing and stub APIs—safe to click through without wallet funds or production credentials.
- What's live — Milestone status on Home (live vs preview vs roadmap, with links).
- Product lines — Launch, Monitor, NodeOps, Secure in the top bar: packaged narratives you can compare before choosing depth.
- Commercial — Pricing → Checkout (RPC verify + receipts) → Plan & usage (stub quotas until billing ships).
- Evidence & SEO — Sitemap and robots are generated; canonical URLs follow
NEXT_PUBLIC_SITE_URL. - Long-form docs — curated links on Documentation, templates preview (roadmap and runbooks in ehx-kb).
Suggested first-run flow
- Skim the persona that matches your role—each section lists outcomes and deep links into the right service previews.
- Open one suite preview (Launch, Monitor, NodeOps, or Secure) and read the “Commercial path & further reading” block at the bottom for how pricing and checkout connect.
- When you are ready to stress the payment UX, open Checkout, create a session, and use the new receipt exports if you need a paper trail for internal testing.
- Keep the roadmap tab open: product names and phases in the UI are aligned with EHX_Roadmap.md so expectations stay honest about what is shipped vs planned.
What best describes you?
Pick a role to highlight the matching path below. No signup—your choice stays in this browser only.
Solo DevOps engineer
Ship faster with less toil—reusable libraries, production-aware defaults, and validation cues you can trust. EHX Launch and Monitor are the default entry points; Secure rounds out posture before you automate more.
- Kubernetes upgrades and ingress without standing up a full platform org.
- Monitoring and security signals that match on-call reality, not vanity charts.
- A single coherent story from cluster defaults to alerts: Launch + Monitor links below are ordered for that walkthrough.
Startup founder
Predictable costs, transparent limits, and a clear upgrade path as the team grows—no ambiguous paywalls. Start with pricing copy, then the checkout stub to see how sessions and receipts behave before real entitlements.
- Public pricing and in-app Plan & usage stay aligned with the API contract as billing ships.
- Crypto-only self-serve checkout is the stated default rail on the roadmap.
- When fundraising or procurement asks for limits in writing, `/pricing` plus exported checkout summaries (stub today) set expectations without overpromising automation.
Web3 protocol team
RPC and validator patterns, security tuned to chain risks, and operational playbooks that match production. Pair NodeOps with Secure before Launch when you are hardening a public RPC or validator fleet.
- NodeOps direction: Ethereum, OP Stack, validators, explorers—documented on the NodeOps preview.
- Secure reviews call out RPC exposure, validator isolation, and backup posture explicitly.
- Launch still matters for how workloads run under the nodes you operate—use it after NodeOps when you are standardizing clusters behind RPC.
AI startup team
Kubernetes automation for training and inference stacks—GPU patterns where applicable, with cost signals later on the roadmap. Treat Monitor as your early warning layer while GPU scheduling templates mature in Launch.
- Launch patterns for durable workloads; Monitor presets for signals you can act on.
- Same transparent commercial model as the rest of EHX—limits stated before you invest deep time.
- When you outgrow default presets, Plan & usage will expose quota headroom; today the page is an API-backed stub you can wire dashboards against later.
Product lines (Launch, Monitor, NodeOps, Secure) are always one click away in the top bar. Use pricing and checkout when you are ready to evaluate commercial boundaries.