Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/fold-faq-into-what-is-agent-native.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@agent-native/core": patch
---

Removed the FAQ docs page and folded its content into What Is Agent-Native and the docs pages each answer actually belonged to (deployment, environment variables, writing agent instructions, templates, key concepts, syncing template changes).
2 changes: 1 addition & 1 deletion packages/core/docs/content/cloneable-saas.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ Four steps take you from template to deployed app:

1. **Pick an app.** Use the CLI picker, or browse the docs.
2. **Brand it.** Change the name, colors, logo, and copy. Most example apps expose this in a single config file.
3. **Customize it.** Make source changes in your own repository and development workflow. An agent can help when its frame is intentionally granted workspace and write tooling; otherwise the embedded agent operates the resulting app through its actions, data, and configured integrations.
3. **Customize it.** Make source changes in your own repository and development workflow: "add a priority field to forms," "connect to our Salesforce instance," "change the color scheme to match our brand." An agent can help when its frame is intentionally granted workspace and write tooling; otherwise the embedded agent operates the resulting app through its actions, data, and configured integrations.
4. **Ship it.** Run the deploy command. You now have a production app at your own domain.

Steps 2–4 typically take a few days. Step 3 has no fixed end point — the app is yours to evolve, while the embedded agent remains available to operate the deployed product and can assist with source changes when code access is explicitly enabled.
Expand Down
11 changes: 10 additions & 1 deletion packages/core/docs/content/deployment.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,16 @@ description: "Deploy agent-native apps to any platform with Nitro presets — No

# Deployment

Agent-native apps use [Nitro](https://nitro.build) under the hood, which means you can deploy to any platform with zero config changes — just set a preset.
Agent-native apps use [Nitro](https://nitro.build) under the hood, which means you can deploy to any platform with zero config changes: just set a preset. Pick any host that runs Node, such as Netlify, Vercel, Cloudflare, AWS Lambda, Deno Deploy, or your own server, paired with any Drizzle-compatible SQL database (Postgres, SQLite, Turso, D1). Nothing here requires Builder.io or any particular cloud; self-hosting the whole stack is a first-class path, not a workaround.

## Cost {#cost}

The framework itself is free: no license fee, and no markup on top of your model provider. In practice you'll see two costs:

- **AI usage.** You bring your own API key (Anthropic, OpenAI, etc.) and pay the model provider directly.
- **Hosting.** Whatever your host charges. Most templates run fine on free tiers (Netlify, Vercel, Cloudflare) for small workloads.

If you'd rather not manage either, the hosted version at `agent-native.com` (operated by Builder.io) bundles inference and hosting into a per-seat plan.

## Fast path: self-host a Chat app locally {#self-host-quickstart}

Expand Down
7 changes: 7 additions & 0 deletions packages/core/docs/content/environment-variables.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,13 @@ multi-user apps should prefer the scoped credential and connection store.
Every provider key below selects its engine on its own: dropping one in is
enough, and `AGENT_ENGINE` is only needed to pick between several.

Supported models span Anthropic Claude, OpenAI (GPT-5 family), Google Gemini,
and any provider that speaks the OpenAI API shape via `OPENAI_BASE_URL`,
including OpenAI-compatible gateways like LiteLLM. The model is chosen in
Settings, so switching providers is a configuration change, not a code
rewrite. Claude is the framework's most heavily tested path and the default
recommendation.

| Variable | What it controls | Supported values or format |
| ------------------------------ | -------------------------------------------------------- | ------------------------------------------------------- |
| `ANTHROPIC_API_KEY` | Claude model fallback for the built-in AI engine. | An Anthropic API key. |
Expand Down
257 changes: 0 additions & 257 deletions packages/core/docs/content/faq.mdx

This file was deleted.

Loading
Loading