> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genieforge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Build apps that evolve from usage

> GenieForge is Living Software: describe an app in plain language, and get a real product with data, pages, automations, and an AI that stays inside after launch.

# Build apps that evolve from usage

GenieForge is a **Living Software** platform. You describe what you need; GenieForge assembles a persistent application from building blocks the AI can operate and evolve: database, pages, forms, tools, roles, automations, a customer portal, and an operator that stays inside after launch.

A coaching practice might get clients, check-in forms, role-specific portals, weekly digests, a companion agent, secure files, and signals when something is missing. Real usage then drives the next version under permissions and rollback.

## Start here

<CardGroup cols={2}>
  <Card title="How GenieForge works" icon="diagram-project" href="/getting-started/how-genieforge-works">
    Blueprint, project, portal, signals, and the evolve loop.
  </Card>

  <Card title="Build your first app" icon="rocket" href="/getting-started/build-your-first-app">
    From first prompt to Preview and inviting end users.
  </Card>

  <Card title="Controlling credits" icon="coins" href="/account/controlling-credits">
    Build vs Chat, active build time, and how to keep spend predictable.
  </Card>

  <Card title="Launch checklist" icon="list-check" href="/getting-started/launch-checklist">
    Access, Preview as, automations, domains, and rollback before go-live.
  </Card>
</CardGroup>

## Get help

* [Troubleshooting](/getting-started/troubleshooting)
* Product how-to, billing, bugs: [support@genieforge.ai](mailto:support@genieforge.ai)
* Privacy: [privacy@genieforge.ai](mailto:privacy@genieforge.ai)
* Website: [https://genieforge.ai](https://genieforge.ai)