# GenieForge

## Docs

- [Availability notes](https://docs.genieforge.ai/account/availability-notes.md): Account-gated and unavailable paths: Marketplace, open routes, share links, HIPAA, and more.
- [Billing, plans, and credits](https://docs.genieforge.ai/account/billing-plans-and-credits.md): How subscriptions and credits work, and where to find current pricing without relying on old quotes.
- [Controlling credits](https://docs.genieforge.ai/account/controlling-credits.md): How Build vs Chat spend credits, what active build time means, and how to keep costs predictable without exact quotes.
- [Credit usage in an app](https://docs.genieforge.ai/account/credit-usage.md): See Build vs Chat credit use, active build time, and spend by person for an app.
- [Getting help](https://docs.genieforge.ai/account/getting-help.md): Where to email support and privacy, and what to include so we can help quickly.
- [HIPAA and regulated health data](https://docs.genieforge.ai/account/hipaa-and-regulated-data.md): For HIPAA, BAA, or PHI, contact support@genieforge.ai. There is no self-serve compliance switch.
- [Marketplace](https://docs.genieforge.ai/account/marketplace.md): Publish or install app blueprints when Marketplace is available; otherwise use export and import.
- [Privacy and compliance](https://docs.genieforge.ai/account/privacy-and-compliance.md): Security posture, privacy contacts, and how to ask GenieForge about certifications without invented claims.
- [Finding past chats](https://docs.genieforge.ai/building/finding-past-chats.md): Search Build, Chat, and end-user conversations under project Chats, and My Chats in the portal.
- [Fork chat from a reply](https://docs.genieforge.ai/building/fork-chat.md): Fork a builder chat from an assistant reply to try a different direction without losing the original thread.
- [How building works](https://docs.genieforge.ai/building/how-building-works.md): How plan-first builds, capabilities, and Build Rules work when you design an app in GenieForge.
- [Second opinion](https://docs.genieforge.ai/building/second-opinion.md): Ask another model for a Second opinion in builder chat without switching the host model or changing the app.
- [Secrets and safe execution](https://docs.genieforge.ai/building/secrets-and-safe-execution.md): Keep secrets out of chat: Environment Variables, secure prompts, outbound network controls, and protected tool execution.
- [Using the AI chat](https://docs.genieforge.ai/building/using-the-ai-chat.md): How Build chat, plans, Second opinion, and Fork chat work in GenieForge.
- [Versions and rollback](https://docs.genieforge.ai/building/versions-and-rollback.md): Your app blueprint is versioned under App Blueprint → Versions so you can roll back recipe changes.
- [Living Software](https://docs.genieforge.ai/concepts/living-software.md): GenieForge builds Living Software: apps where data, workflows, permissions, and AI are one evolvable whole.
- [Usage-Driven Development](https://docs.genieforge.ai/concepts/usage-driven-development.md): How GenieForge closes the loop from real usage to the next version of your app.
- [Apps, projects, and product surfaces](https://docs.genieforge.ai/getting-started/apps-projects-and-surfaces.md): How apps, projects, Build mode, Chat mode, Preview, the portal, and General chat fit together in GenieForge.
- [Build mode vs Chat mode](https://docs.genieforge.ai/getting-started/build-mode-vs-chat-mode.md): Build mode designs the blueprint; Chat mode uses what already exists. Know when to switch.
- [Build your first app](https://docs.genieforge.ai/getting-started/build-your-first-app.md): Create a GenieForge app from a prompt, approve a plan, try Preview, and invite end users.
- [Export and import](https://docs.genieforge.ai/getting-started/export-and-import.md): Export and import an app blueprint to back up, move environments, or share a starting recipe (not project customer data).
- [How GenieForge works](https://docs.genieforge.ai/getting-started/how-genieforge-works.md): The Living Software loop: blueprint, project runtime, portal, operator AI, signals, and versioned change.
- [Launch checklist](https://docs.genieforge.ai/getting-started/launch-checklist.md): A practical checklist before you treat a GenieForge project as live for real customers.
- [Starting from your first prompt](https://docs.genieforge.ai/getting-started/starting-from-your-first-prompt.md): Ways to begin building on GenieForge: plain-language prompts, plan-first builds, and constraints that stick.
- [Troubleshooting](https://docs.genieforge.ai/getting-started/troubleshooting.md): Fix common GenieForge issues: role access, automations, OAuth, domains, forms, credits, and unexpected Build changes.
- [What GenieForge is](https://docs.genieforge.ai/getting-started/what-genieforge-is.md): GenieForge is a Living Software platform that uses a conversational builder to assemble persistent apps from AI-operable building blocks.
- [Writing better prompts](https://docs.genieforge.ai/getting-started/writing-better-prompts.md): Prompt patterns that get clearer GenieForge builds faster.
- [Build apps that evolve from usage](https://docs.genieforge.ai/index.md): 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.
- [Connected accounts (OAuth)](https://docs.genieforge.ai/integrations/connected-accounts.md): Connect OAuth providers from App Settings → Integrations without pasting tokens into chat.
- [HTTP APIs and web data](https://docs.genieforge.ai/integrations/http-apis-and-web-data.md): Call external HTTP APIs safely, and optionally use Web Data Sources when enabled for your account.
- [Inbound routes and webhooks](https://docs.genieforge.ai/integrations/inbound-routes.md): Inbound routes let outside systems call your tools, protected by bearer tokens or signed webhooks.
- [Background tasks](https://docs.genieforge.ai/logic/background-tasks.md): Run long jobs in the background and track them under project Executions.
- [Evals](https://docs.genieforge.ai/logic/evals.md): Define conversation test cases and re-run them after changes so critical chat flows stay solid.
- [Event hooks](https://docs.genieforge.ai/logic/event-hooks.md): Event hooks run when tools, records, forms, or jobs finish, so follow-ups do not depend on chat.
- [Notifications](https://docs.genieforge.ai/logic/notifications.md): Reach people by email, in-app inbox, push (when enabled), or webhook, with templates and digests.
- [Scheduled automations](https://docs.genieforge.ai/logic/scheduled-automations.md): Scheduled automations run on a timetable in a project: digests, reminders, nightly syncs, and more.
- [App files vs project files](https://docs.genieforge.ai/managing-data/app-files-vs-project-files.md): App files travel with the blueprint; project files stay with one project's uploads and exports.
- [Data structure](https://docs.genieforge.ai/managing-data/data-structure.md): Define tables through migrations; GenieForge keeps data models in sync for tools and the AI.
- [Seed data](https://docs.genieforge.ai/managing-data/seed-data.md): Starter data for new projects so empty workspaces feel ready (not a substitute for real customer data).
- [Agents](https://docs.genieforge.ai/primitives/agents.md): Agents give different audiences their own instructions, tools, and chat branding inside one app.
- [Build rules](https://docs.genieforge.ai/primitives/build-rules.md): Build Rules are lasting conventions for how the AI should build your app across every Build conversation.
- [Documentation](https://docs.genieforge.ai/primitives/documentation.md): App Blueprint → Documentation records important build decisions so future changes do not undo them.
- [Forms](https://docs.genieforge.ai/primitives/forms.md): Forms collect structured fields (with optional public intake links and QR codes) better than multi-turn chat.
- [Libraries](https://docs.genieforge.ai/primitives/libraries.md): Libraries are shared code helpers that several tools can reuse, and they travel with export and import.
- [Navigation](https://docs.genieforge.ai/primitives/navigation.md): Configure the route tree: groups, breadcrumbs, role gates, and what end users see in the portal sidebar.
- [Pages](https://docs.genieforge.ai/primitives/pages.md): Pages are real app screens (tables, dashboards, forms, chat) that load without calling the AI on every visit.
- [Sub-agents](https://docs.genieforge.ai/primitives/sub-agents.md): Sub-agents run focused AI jobs with inputs and a result, without a back-and-forth conversation.
- [Tools](https://docs.genieforge.ai/primitives/tools.md): Tools are secure custom actions your app runs: create records, call APIs, and power pages and forms.
- [Views (AI reports)](https://docs.genieforge.ai/primitives/views.md): Views are saved AI report templates for recurring analysis in a project.
- [Custom domains for a project](https://docs.genieforge.ai/projects-and-domains/custom-domains.md): Put a project on your own subdomain with CNAME, TXT verify, and SSL from Project Settings.
- [Customer portal](https://docs.genieforge.ai/projects-and-domains/portal.md): How end users sign in and use your GenieForge app through the portal.
- [Projects](https://docs.genieforge.ai/projects-and-domains/projects.md): Projects are isolated runtimes of the same app, each with its own database and files.
- [Platform feedback](https://docs.genieforge.ai/usage-and-improvement/platform-feedback.md): Tell the GenieForge team about platform gaps or bugs via Platform Feedback.
- [Signals and in-app feedback](https://docs.genieforge.ai/usage-and-improvement/signals-and-feedback.md): Signals capture real usage friction so you know what to build next, including app vs platform tags.
- [Builder team access](https://docs.genieforge.ai/users-and-access/builder-team-access.md): Invite builder collaborators (Owner, Admin, Editor, Viewer) separately from end users.
- [Inviting and managing end users](https://docs.genieforge.ai/users-and-access/inviting-end-users.md): Invite customers to the portal, choose roles, and configure Project or App Registration.
- [Memories](https://docs.genieforge.ai/users-and-access/memories.md): Optional agent memories keep useful facts about a person across conversations (not a substitute for structured data).
- [Preview as a role](https://docs.genieforge.ai/users-and-access/preview-as.md): Try the customer experience as any role without inviting a real person.
- [Reviewing app access](https://docs.genieforge.ai/users-and-access/reviewing-app-access.md): Use App Blueprint → Access to map what each role can reach and catch common permission mistakes.
- [Roles and access control](https://docs.genieforge.ai/users-and-access/roles-and-access-control.md): Roles control which tools, forms, pages, and data each end user can reach.