> For the complete documentation index, see [llms.txt](https://developers.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.felt.com/plans-access-and-limits.md). # Plans, access and limits What each plan includes for developers, and what happens at a limit. For prices, see [felt.com/pricing](https://felt.com/pricing). ## Which plan do I need? | Feature | Plan | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | | Standard embeds of public or unlisted maps | Team and up | | [JS SDK](/js-sdk/getting-started.md) and [authenticated embeds](/js-sdk/authenticated-embeds.md) | Platform add-on, on Team and up | | [REST API](/rest-api/getting-started.md), [webhooks](/rest-api/listening-to-updates-using-webhooks.md), [MCP](/ai-agents-and-mcp.md) and [Extensions](https://help.felt.com/dashboards-and-apps/extensions) | Business and Enterprise | | Database, warehouse and private cloud bucket connections | Business (1), Enterprise (unlimited) | **Trial.** Every new workspace gets 7 days of Business with Platform, with no credit card. It ends on the Free plan unless you choose a paid one. ## Platform Platform is the add-on for building your own product on Felt. It includes the JS SDK, authenticated embeds, and commercial rights to sell what you build. It works with any paid plan, and the first three months are free. Your app's users don't need Felt accounts, seats or viewer spots; each map load counts as a map view. On Team, Platform includes the embed-token endpoint, though not the rest of the REST API. Embeds show Felt attribution. Enterprise can remove it with the Custom Branding add-on. ## Monthly limits | | Free | Team | Business | Enterprise | Trial | | --------------- | ------ | ------ | -------- | ---------- | ------ | | Map views | 10,000 | 25,000 | 100,000 | 250,000 | 25,000 | | Processing | — | 5 GB | 25 GB | 100 GB | 5 GB | | Storage | — | 20 GB | 100 GB | 400 GB | 20 GB | | Felt AI credits | — | 250 | 1,000 | 2,500 | 250 | | Fastest refresh | — | Daily | Hourly | 15 minutes | Hourly | * **Map views** count every load of a map: on felt.com, in an embed, or in your app. If you're building an app, this number grows with your users. * **Processing** counts uploads, refreshes and analysis outputs. Each refresh counts the full dataset, so a table refreshed hourly counts about 720 times a month. Streamed vector tiles and Cloud Optimized GeoTIFFs don't count. * **Felt AI credits** are used by Felt AI and the MCP tools that call it (`generate_fsl`, `developer_docs`, `help_center`). * **Data connections**: one connection is one database, warehouse, bucket or STAC catalog, with any number of tables. Public URLs, ArcGIS, WMS/WFS, Google Sheets and SharePoint don't count. The REST API also allows 300 requests per minute per IP address; see [Errors and rate limits](/rest-api/errors-and-rate-limits.md#rate-limits). ## At a limit Existing maps keep working. Felt never charges for overage automatically: admins get warnings at 80% and 100%, and can add usage packs from billing settings (not during a trial). | Limit | What happens | | --------------------- | -------------------------------------------------------------------------------------------------------- | | Map views | Public visitors and all embeds see an over-limit page. Workspace members can still open maps. | | Processing or storage | Uploads and refreshes pause. The API returns `403` with `over_processing_limit` or `over_storage_limit`. | | Data connections | New connections return `403` with `over_data_connection_limit`. | | Refresh schedule | A schedule faster than your plan allows returns `422`. | | Felt AI credits | AI requests wait until the 1st; other MCP tools keep working. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developers.felt.com/plans-access-and-limits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.