# Overview

Source: /docs/features/overview

Beyond hosting, the platform adds business features to your app without you running the services behind them. This page is the map; each feature has its own guide.

## The groups [#the-groups]

* **User accounts** — sign-up and login for your app's end users. When enabled, an `auth` schema appears in your database and the platform owns it; your app reads it. See [what runs here](/docs/getting-started/what-runs-here).
* **Payments** — Stripe Connect, a product and price catalog, checkout, and a paid state your app can check.
* **Add-ons** — extras such as **traffic analytics** for your app.

Which features you can turn on depends on your [plan](/docs/concepts/plans-and-quotas).

## Enable, configure, wire [#enable-configure-wire]

Most features follow the same three steps:

1. **Enable** — turn the feature on for the app. Some choices are permanent: user accounts, once enabled, cannot be turned off.
2. **Configure** — set it up in the dashboard (for example, finish Stripe onboarding, or create products and prices).
3. **Wire** — connect your app's code to the feature. The dashboard gives you a **wiring prompt** to paste into your coding agent, which edits your code to read the feature.

After enabling or wiring a feature, your app usually needs a **deploy** to pick it up. The dashboard shows a pending state until you do.

## Doing it through a coding agent [#doing-it-through-a-coding-agent]

An agent connected over [MCP](/docs/mcp/overview) can enable features, configure catalogs, and pull the wiring prompt for you. It cannot create or verify your Stripe account — do that yourself first, then the agent can enable payments, create products and prices, and wire the paywall.

## The guides [#the-guides]

* [Payments](/docs/features/payments)
* [User accounts](/docs/features/auth)
* [Traffic analytics](/docs/features/analytics)