Getting started
Sign up, create a feature, and read it from the client app in under five minutes.
1. Create an account
Go to app.featuretoggle.com and sign up. The organization is the team workspace. Use the organization switcher in the header to create or select one, and invite teammates from Manage.
2. Create a project
On Projects, click Create project. A project is the container for features, environments, and API keys. FeatureToggle does not prescribe one project per app versus one project for many deployables. Pick the layout that fits the setup:
| Layout | When it fits |
|---|---|
| One project | Client SPA and API share the same features and environments |
| Multiple projects | Deployables need independent feature sets |
Creating a project seeds a development environment automatically. You cannot rename or delete development.
3. Create a feature
In the dashboard: open the project → Feature definitions → Create feature.
| Field | Notes |
|---|---|
| Name | Display label in the dashboard (client code uses Key). |
| Key | Stable identifier client code uses (e.g. new-checkout). Immutable after create. 1-64 characters, starts with a letter, and matches ^[a-zA-Z][a-zA-Z0-9_-]*$. |
| Type | boolean, string, number, or json |
| Default value | Resolved value when the feature is off, or when enabled with no custom override (usesDefault). New boolean features default to false. |
4. Enable in development
Features are off in every environment until you activate them. In the dashboard, go to Environments → development → Features and turn on the feature with the switch in the first column.
5. Create an API key
In the dashboard: Environments → development → API keys → Create key.
- The full key is shown once. Copy it immediately.
developmentkeys use theft_test_prefix.- Each key is scoped to one environment.
6. Connect the client app
Open SDKs for packages and Cookbook links. Call the Feature API directly if you skip the SDK.
7. Toggle and verify
- Run the client app with the SDK or API client initialized.
- In the dashboard, change the feature under development → Features (switch or value edit).
- Confirm the change in the client app. Caching explains how updates reach clients.
Next steps
| Topic | Doc |
|---|---|
| SDK packages and Cookbooks | SDKs |
| Per-environment overrides | Core concepts |
| Deploy to staging/production | Core concepts · Security |
| API without the SDK | Feature API reference |
| Security before production | Security |