Billing & Usage
FoxNose uses a unit-based billing system. Every plan includes a set of units that cover API requests, storage, and other operations. This page explains how your usage is measured, what happens when you run out of units, and how plan changes work.
Open Beta — FoxNose is currently in open beta. During this period, only the free plan is available. If you find that the included limits are not enough for testing the product in real-world conditions, you can request additional capacity by contacting our support team at support@foxnose.net.
How Billing Works
Each plan includes a monthly allocation of units. Units are a universal currency that covers all billable operations in FoxNose. Every billing cycle lasts one month from the date you activated your plan.
At the start of each billing cycle, your unit balance is reset to the amount included in your plan.
What Consumes Units
Units are consumed by the following types of operations:
API Requests
Every API request to the Flux API or Management API consumes units, including requests that return client errors (4xx). Only internal server errors (5xx), rate-limit responses (429), and preflight (OPTIONS) requests are not charged.
Vector Operations
- Vectorization — computing vector embeddings for semantic search consumes units when vectors are created or updated.
- Vector Search — querying your data using semantic (vector) search consumes units per request.
Storage
Your data and vector storage are measured continuously throughout the billing cycle. The average storage usage is calculated and deducted from your unit balance periodically.
- Data Storage — the total size of your resources and content.
- Vector Storage — the total size of stored vector embeddings used for semantic search.
Storage costs are based on average usage over time, not peak usage. Temporary spikes will not disproportionately affect your bill.
Plan Limits
In addition to units, each plan defines fixed limits on platform resources:
| Resource | Description |
|---|---|
| Projects | Maximum number of projects in your organization |
| Environments | Maximum number of environments across all projects |
| Folders | Maximum number of folders |
| Resources | Maximum number of resources |
| Users | Maximum number of users in your organization |
| Components | Maximum number of components |
| API Keys | Maximum number of API keys per environment |
| Roles | Maximum number of roles per environment |
| Locales | Maximum number of locales per environment |
| Schemas | Maximum number of schema versions |
| Schema Fields | Maximum number of fields per schema |
| Flux APIs | Maximum number of Flux APIs per environment |
These limits are enforced in real time. If you reach a limit, you will need to upgrade your plan or remove existing resources before creating new ones.
Running Out of Units
When your unit balance reaches zero, FoxNose restricts access to your organization's API services. While restricted:
- API environments are paused.
- Flux API and Management API requests will return errors.
- You can still access the FoxNose dashboard to manage your plan.
To avoid service interruption, monitor your unit balance on the usage dashboard and upgrade your plan before running out of units.
Full access is automatically restored when a new billing cycle begins or when you upgrade to a higher plan.
Changing Plans
You can change your plan at any time from the organization settings.
Upgrading
When you switch to a higher plan, the change takes effect immediately:
- Your remaining units from the current cycle carry over to the new plan.
- A new billing cycle starts with the upgraded plan's unit allocation, plus any leftover units.
- If your organization was restricted due to running out of units, full access is automatically restored.
Downgrading
When you switch to a lower plan, the change is scheduled:
- Your current plan remains active until the end of the billing cycle.
- The new plan activates at the start of the next billing cycle.
- You continue to use your current plan's units and limits until the switch happens.
You can see your scheduled plan change in the organization settings. The active plan and the upcoming plan are displayed separately.
Billing Cycle
- Each billing cycle is one month long, starting from the day you activated or last renewed your plan.
- At the start of a new cycle, your unit balance is replenished with the units included in your active plan.
- If a plan change was scheduled (downgrade), it activates at the start of the new cycle.
- If your organization was restricted due to running out of units, full access is automatically restored when the new cycle starts.
Monitoring Usage
You can track your organization's usage in the FoxNose dashboard:
- Unit balance — your remaining units for the current billing cycle.
- API requests — total requests made during the current cycle.
- Storage usage — current data and vector storage consumption.
We recommend checking the usage dashboard regularly to stay ahead of your plan limits and avoid unexpected interruptions.
FAQ
What happens to my data if my organization is restricted? Your data is safe. The restriction only pauses API access. Once access is restored (via a new billing cycle or plan upgrade), everything works as before.
Can I switch plans multiple times? Yes. You can upgrade immediately at any time. If you schedule a downgrade, you can change your mind and select a different plan before the cycle ends.
Do unused units roll over to the next cycle? No. Unit balances are reset at the start of each billing cycle. Unused units do not carry over, except when upgrading mid-cycle — in that case, remaining units are added to the new plan's allocation for that cycle only.
Are failed API requests charged?
Most requests consume units, including those that return client errors (4xx). However, internal server errors (5xx), rate-limit responses (429), and preflight (OPTIONS) requests are never charged.