--- title: "Free plan FAQs" canonical: "https://support.apollographql.com/space/ETKB/1297809476/Free%20plan%20FAQs" format: markdown --- | #### đźš© Launched 19 Feb 2025 - this plan is the default for anyone who signs-up directly via [http://www.apollographql.com/signup](http://www.apollographql.com/signup) No more trial period or getting locked out of your account. | | --- | | **Questions** | **Answers** | | --- | --- | | ### **Does Free Plan fit my needs?** | Choose Free if:
- You're learning GraphQL or prototyping new ideas - You’re not yet ready to use GraphOS Router in a production use case with real users - Your team has 3 or fewer members - You want to explore Apollo's capabilities risk-free | | ### **What does Free Plan Include?** | **All Free Plans include:**
- Up to 3 members within the org - 1 day of data retention (insights, checks, traces) - Support via the Apollo Community
**Self-hosted GraphOS Router (capable of running Apollo Connectors for REST)**
- 60 requests / minute per router instance - 1 router instance per variant | | ### **What does Free Plan not Include?** | The Free Plan does not include:
- Single Sign On - Dedicated support plans (standard support, or premium support packages) - GraphOS Router extensibility features (such as external coprocessors) - Cross-team collaboration tools (e. Schema Proposals, configurable Linting Checks) - Audit History | | ### **What happens if I exceed the runtime throughput limit?** | Operations in excess of the limit will be dropped (returning a 503 service temporarily unavailable error). This behavior is similar to what would happen if someone were to implement the same global throughput limit through [traffic shaping](https://www.apollographql.com/docs/graphos/routing/performance/traffic-shaping). | | ### **How will I know if I exceed the runtime throughput limit?** | - Approaching a limit: We do not have anything in the product today to warn of a given router approaching the rate limit. - Limit is hit: The request will result in a **503 Service Unavailable** error. Currently, visibility into these errors depends on your observability setup for deployed router logs and any monitoring in place for HTTP responses/response codes. | | ### **If I encounter this limit, can I self-serve to upgrade?** | At this moment, there is no way to self-serve upgrade to a paid plan with a higher limit. For more information on our plans, see our pricing page. [https://www.apollographql.com/pricing](https://www.apollographql.com/pricing) | | ### **Can I request a higher limit?** | You can request a higher limit as part of upgrading to a paid GraphOS plan. For more information on our plans, see our pricing page. [https://www.apollographql.com/pricing](https://www.apollographql.com/pricing) | | ### **Can I move my current trial org into the free plan? ** | No, but you can easily create a new organization and publish any existing GraphQL APIs / schemas to that new organization on the Free plan. Within GraphOS Studio:
- Click on your organization name in the upper left corner to open the dropdown - Click on “Create a new organization”
Then, if you have prior work, you can publish those [existing schemas](https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/publish#publish-monograph-schemas) to the new organization. | | ### **I’m on a trial now. Will Apollo proactively move my org to the Free plan when it expires? ** | No, the GraphOS Trial and Enterprise Trial offers some functionality not available on the Free Plan. As such, it will still be locked at the end of the trial period. You are welcome to create a new organization on the Free plan and move your work there. | | ### **What can I do with GraphOS if I’m running a single GraphQL server or not using federated GraphQL?** | All graphs can immediately benefit from the GraphOS API Development Platform. Get instant observability, including errors and traces, and all of the benefits of schema registry the moment you connect your graph to GraphOS. Similarly, all GraphQL developers can equip themselves with the best available development tools from Apollo, covering IDE extensions, client SDKs, and more. With Apollo, you can reach for graph orchestration (via federated architectures) whenever you have an orchestration problem. For help publishing your graph, [visit our documentation](https://apollographql.com/docs/graphos/platform/schema-management/delivery/publish#publish-monograph-schemas). | | ### **What can I do with GraphOS if I’m not yet using GraphOS Router?** | Any GraphQL API - whether using Apollo Server, Apollo Gateway, or another server framework - will still immediately benefit from the Apollo Studio management layer for observability, schema registry, and user management. Likewise, you will still benefit from Apollo’s developer tools, such as IDE extensions, client SDKs, and more. | | ### **Does the Free plan support Connectors?** | Yes. This Free plan has been designed with Connectors at the center of the user experience. | | ### **Does the Free plan support self hosted or Apollo-hosted graphs?** | The Free plan currently only supports self-hosting. We plan to reintroduce Apollo-hosted (“serverless”) graphs in the future, but do not have a committed date for a public launch of that option. | | ### **What do I do if I’m on Apollo’s Serverless Free plan?** | If you’re on the Serverless Free plan, nothing changes! You can still continue to use your plan as before, though we encourage you to sign up for the new Free plan to benefit from Apollo Connectors for REST, self-hosted GraphOS Router, and more. | | ### **What level of support do Free plan users expect to receive from Apollo?** | Free plan users will be encouraged to leverage our self-serve resources, including the Docs, Odyssey and Help Center. They will also have access to our [Apollo Community](https://community.apollographql.com/) Forum, where they can share insights, ask questions, and find practical solutions to common challenges posted by verified community members and Apollonauts. Finally, these users will have limited access to Technical Support to submit bug reports, enhancement requests, and for account-related issues with no publicly stated SLA. For all other issues, they will be directed toward the [Apollo Community](https://community.apollographql.com/) for support. |