Getting Started

    Launch your first AeThex project in under 30 minutes

    This guide walks through the minimum setup required to ship a production-ready AeThex application. Complete the prerequisites, initialize a workspace with the CLI, and review the deployment checklist before inviting collaborators. Use the platform highlights below to brief product, community, and live-ops teams on everything available beyond deployment.

    Create an AeThex account (full)

    Step 1 — Choose sign-in method

    AeThex supports Email/password, OAuth providers, and Web3 wallet sign-in.

    1. Email sign-up: go to /signup, provide your email and a secure password. A verification email will be sent — click the link to confirm.
    2. Google / GitHub: click the provider button on /login. The first time you sign in we'll create your account automatically using the provider email.
    3. Discord: use "Continue with Discord" on the login page. Existing accounts with the same email will be linked, otherwise a new account is created. For linking flows for existing staff, see the Dashboard → Connections.
    4. Web3 (optional): sign-in with Ethereum wallet via MetaMask — used only for wallet verification and account linking (no custody).

    Step 2 — Verify & complete profile

    After initial login you'll be prompted to complete onboarding (profile, bio, primary arm).

    1. Check your email and follow the verification link (email provider flow).
    2. Complete the onboarding steps including name, bio, interests, and primary arm selection.
    3. Link any additional providers from Dashboard → Connections if needed.
    4. Once finished click "Finish & Go to Dashboard" to start using the platform.
    Notes & troubleshooting
    • If an OAuth provider reports "account exists", sign in using the original provider and then link the new provider from Dashboard → Connections.
    • If you don't receive verification emails, check spam and ensure no company email filtering blocks support@aethex.tech.
    • Staff accounts (aethex.dev emails) may receive additional role access; contact HR if you expect staff access and it doesn't appear after login.

    Documentation categories

    Jump into the area you need most. Each category below is mirrored in Builder CMS for collaborative editing.

    12 docs

    Getting Started

    Quick start guides and tutorials for beginners

    • Installation
    • First Steps
    • Basic Concepts
    • Hello World
    45 docs

    API Reference

    Complete API documentation with examples

    • Authentication
    • Endpoints
    • SDKs
    • Rate Limits
    28 docs

    Tutorials

    Step-by-step guides for common use cases

    • Game Development
    • Web Apps
    • Mobile Apps
    • AI Integration
    15 docs

    CLI Tools

    Command-line interface documentation

    • Installation
    • Commands
    • Configuration
    • Scripts

    AeThex Account

    You will need an active AeThex account to access the dashboard, API console, and deployment tools.

    Create account

    Node.js 18+ & npm

    The AeThex CLI relies on modern Node runtimes. Verify your local toolchain before continuing.

    Verify environment

    Project Workspace

    Choose an empty directory for your new AeThex project or clone an existing team template.

    Browse templates

    Onboarding — what to expect

    Onboarding is a guided, multi-step flow that helps users complete the essential profile and platform setup. Typical onboarding steps:

    1. Personal Info — name, display handle, avatar.
    2. Profile Type — select experience level and role (creator, studio, enterprise).
    3. Interests & Skills — choose tags so we can recommend opportunities and mentors.
    4. Choose Primary Arm — pick the arm that best represents your work (Labs, GameForge, Corp, Foundation, Dev-Link).
    5. Creator Profile — optional portfolio, bio, links (recommended for discoverability).
    6. Finish — background tasks run (profile refresh) and you land on the dashboard.

    You can always update these later from Profile → Settings.

    Explore the platform

    Unified dashboard

    Monitor deployments, review incidents, and share announcements with stakeholders from a single console.

    Passport identity

    Give every builder a portable profile that aggregates achievements, verified skills, and mentorship history.

    Community and mentorship

    Pair emerging studios with advisors, host showcase events, and recruit collaborators through the community hub.

    Live ops analytics

    Track real-time KPIs, automate status updates, and route alerts into your team's notification channels.

    Setup workflow

    Step 1

    Install the CLI

    The CLI bootstraps local projects, provisions cloud environments, and manages deployments.

    npm install -g aethex
    Step 2

    Authenticate

    Log in with your AeThex credentials or paste a personal access token from the dashboard.

    aethex login
    Step 3

    Initialize a Project

    Scaffold configuration, environment files, and example services for your team.

    aethex init studio-hub
    Step 4

    Start the Dev Server

    Run the local environment with hot reloading, mocked services, and seeded sample data.

    npm run dev

    Configure Environments

    Define staging and production targets, secrets, and automated health probes in aethex.config.ts.

    Provision Resources

    Use `aethex deploy --preview` to create sandbox infrastructure before promoting to production.

    Enable Safeguards

    Turn on role-based access controls, audit logging, and automated rollbacks from the dashboard.

    Staff editing & governance

    This public documentation is the platform-facing view. Internal operational documents remain private under /internal-docs.

    Editors (staff) can edit public docs using Builder CMS. After changes are reviewed in Builder, create a GitHub PR to push finalized content into the repository so it can be deployed with site updates.

    • Edit in Builder: Open MCP popover and select Builder.io to edit live doc components and page content. (Staff only)
    • Publish workflow: Use the Builder preview to validate changes, then export or commit the markdown/content and open a GitHub PR for review. CI runs will deploy the updated public docs.
    • Security: Internal API references are intentionally not included in public docs. If you need to publish API guides for partners, request a gated partner docs area.

    Next steps

    Platform Walkthrough

    Tour the dashboard, notification center, and collaboration features.

    Explore

    Platform documentation

    Share the high-level platform overview with non-technical teammates.

    Explore

    API Reference

    Review authentication flows, REST endpoints, and webhook schemas.

    Explore

    Tutorial Library

    Follow guided builds for matchmaking services, player analytics, and live events.

    Explore

    Community Support

    Ask questions, share templates, and pair up with mentors in the public forums.

    Explore

    Integrations Playbook

    Review the HelloSkip embed and extend it to other partners.

    Explore