SimplifyAccess provides different subscription plans to support individual websites, growing teams, and organizations managing multiple domains.
Each plan includes a set of features and resource allowances that determine how extensively you can use the platform.
These allowances cover website management, accessibility reporting, API requests, content-processing tasks, and support services.
The Usage card on your Dashboard helps you monitor resource consumption and understand how much of your available allowance has been used.
In this guide, you'll learn:
- Which resources are subject to limits
- Which limits apply to individual websites or your entire account
- How API requests and processing jobs are counted
- When monthly allowances renew
- How to find the allowances included in your subscription
For current allowances, see the SimplifyAccess Pricing Plans.
1. Where to Find Your Usage Information
You can review usage information directly from the SimplifyAccess Dashboard.
- Sign in to your SimplifyAccess account.
- Select the website or controller you want to review.
- Open the Dashboard.
- Locate the Usage card.
The card displays available usage indicators, including resource counters, progress bars, and applicable reset dates.
For example, an indicator might show:
API calls: 215 / 100,000
This means 215 API calls have been recorded against an allowance of 100,000 calls for the applicable period.
The progress bar provides a visual indication of how much of that allowance has been consumed.
Some resources, such as domain changes and support tickets, may be managed or displayed elsewhere in the platform rather than appearing in the Dashboard's Usage card.
Controller-Specific Usage
Each website in SimplifyAccess is managed through a controller.
Most resource allowances apply individually to each controller, meaning that the activity associated with one website does not consume another website's separate allowance.
The exception is support tickets, which are counted at account level and shared across all controllers.
For more information about selecting controllers and navigating the Dashboard, see Understanding the Dashboard.
Overall Usage Across All Controllers
You can also view your combined resource usage on the Controllers Overview page.
The page displays your registered controllers, their individual API and job usage, and an Overall Usage summary.
If your account contains only one controller, the summary reflects the usage of that single website.
If you manage multiple controllers, the summary combines their usage into a single overview, including API calls, processing jobs, developer emails, and generated reports.
This makes it easy to monitor resource consumption across all your websites without switching between individual Dashboards.
2. Understanding the Different Resource Limits
SimplifyAccess distinguishes between the number of websites you can manage, the amount of content covered by your plan, and resources consumed through ongoing platform activity.
The following table summarizes the available allowances.
| Resource | What it measures | Applies to |
|---|---|---|
| Websites or domains | Number of websites included in your subscription | Account |
| Maximum pages | Number of pages allowed for an individual website | Controller/domain |
| Reports per month | Number of generated reports | Controller/domain |
| Domain changes per month | Changes to the registered website domain | Controller/domain |
| Developer emails per month | Messages sent to a designated address | Controller/domain |
| Support tickets per month | Support requests submitted through the account | Account |
| API requests | Requests made through supported API-based features | Controller/domain |
| Jobs | Manually triggered processing operations | Controller/domain |
The limits included in your subscription depend on the selected plan.
Rather than relying on fixed numbers in this guide, check the current allowances for your plan:
3. Websites and Domains
Your subscription determines how many websites or domains you can manage within your SimplifyAccess account.
Each website is associated with its own controller, including its configuration and accessibility data.
For example, an organization managing several separate websites may need a plan supporting multiple controllers.
The Agency plan is designed for this purpose, while Standard and Pro focus on individual websites.
Managing Multiple Websites
When your plan supports multiple websites, each controller maintains its own resources and settings.
This makes it possible to manage several websites from one account while keeping their accessibility information separate.
The website allowance is a subscription capacity, rather than a monthly activity counter.
Learn more about multi-website management in the Agency Plan.
4. Maximum Pages
The Maximum Pages allowance determines how many pages can be included within an individual controller's permitted page capacity.
This is particularly relevant for websites with many subpages, such as:
- Large organizational websites
- Online service portals
- Websites with extensive article collections
- Multi-department or multi-location websites
For example, a website with 120 discovered pages requires an allowance large enough to accommodate those pages.
Why Does the Page Limit Matter?
SimplifyAccess manages page-level accessibility information, including audit results and supported content workflows.
The page allowance defines the permitted scope of the website within the selected subscription.
Unlike monthly reports or API requests, the maximum page allowance is a capacity limit.
It does not mean you receive a new set of pages to consume each month.
Tip: If you expect your website to grow substantially, choose a plan with enough page capacity for future content.
For an overview of page-level accessibility management, explore Site Workspace.
5. Reports per Month
The Reports allowance determines how many accessibility reports can be generated for a controller during a subscription month.
Reports help you document website accessibility findings, communicate progress, and share information with relevant stakeholders.
When Are Reports Counted?
Generating a report consumes the applicable report allowance.
For example, if you generate several reports during the same subscription month, each generation counts against the available monthly quota.
The allowance renews when the next subscription month begins.
Reports and Processing Jobs
Report generation may also count toward your processing job allowance because it is a manually initiated platform operation.
These are different resource counters:
- The Reports allowance controls the number of reports generated.
- The Jobs allowance controls the permitted number of manually triggered processing actions.
For more information about reporting, visit Accessibility Reports.
6. Domain Changes per Month
The Domain Changes allowance determines how often you can change the registered domain associated with a controller during a subscription month.
This may be useful when:
- Moving a website to a new domain
- Renaming an organization or website
- Changing a project's primary domain
- Reconfiguring a website during development or migration
A domain change is different from adding another website.
Changing the registered domain updates an existing controller, while adding another website requires an available website or domain slot.
Domain changes are counted separately for each controller.
Tip: Before changing a registered domain, make sure the new domain is correct and that any necessary website integration changes have been prepared.
7. Developer Emails per Month
SimplifyAccess provides an allowance for messages sent to a designated email address, such as your developer's or technical contact's address.
This can support communication about accessibility findings or technical work requiring attention.
How Are Developer Emails Counted?
The allowance is based on messages sent, not the number of unique recipients or the number of issues discussed.
For example:
- Sending one message counts as one developer email.
- Sending another message later counts as an additional developer email.
The allowance applies individually to each controller.
Developer emails are distinct from support tickets submitted to SimplifyAccess.
8. Support Tickets per Month
Support tickets allow you to request assistance from the SimplifyAccess support team.
Unlike most usage allowances, support tickets are counted per account rather than per controller.
Shared Account Allowance
If your account manages multiple websites, they share one monthly support ticket allowance.
For example, a support request concerning Website A and another concerning Website B both count toward the same account allowance.
This is particularly important for Agency customers managing multiple projects.
Support tickets are not multiplied by the number of websites included in the subscription.
You can access support through the SimplifyAccess Customer Support environment.
9. API Requests
The API allowance measures requests made through SimplifyAccess's supported API-based functionality.
API requests support important integrations and content-delivery features across the platform.
These may include:
- Accessibility Widget requests
- Delivery of alternative or simplified content
- Video transcription-related API functionality
- Programmatic use of the SimplifyAccess API
What Counts as an API Request?
An API request is an interaction with a supported API endpoint that is counted against your usage allowance.
Such requests may be initiated by website integrations, visitor-facing features, or applications using the SimplifyAccess API.
This means API usage is not necessarily the same as the number of visitors to your website.
A single visitor may trigger multiple requests, while some website interactions may not trigger any countable API requests.
Understanding API Consumption
Suppose your website uses SimplifyAccess to provide alternative content through its accessibility integration.
When supported content is requested through the API, those interactions can contribute to your API usage.
The exact number of requests depends on how the feature is used and integrated.
Monitoring API Usage
The Dashboard's Usage card shows the number of API calls recorded against the applicable allowance.
Check this indicator regularly if your website receives substantial traffic or uses SimplifyAccess programmatically.
Learn more about the visitor-facing integration on the Accessibility Widget page.
10. Processing Jobs
The Jobs allowance covers manually triggered processing operations within SimplifyAccess.
Jobs are different from API requests.
An API request generally involves requesting information or functionality through an API endpoint.
A processing job involves instructing SimplifyAccess to perform a task.
Examples of Processing Jobs
Depending on your available features, manually initiated operations may include:
| Operation | Purpose |
|---|---|
| Accessibility report generation | Generate a report using available accessibility information |
| Re-crawling content | Retrieve or process website content again |
| Regenerating alternative content | Create updated alternative content after changes |
These operations consume resources and therefore count toward the applicable processing job allowance.
When Might You Need Additional Jobs?
Processing jobs are particularly relevant when you regularly update website content or manually repeat processing operations.
For example, after substantially changing a website, you might want to re-crawl affected content or regenerate its alternative versions.
These actions may consume additional jobs.
Tip: Plan larger batches of manually initiated work and avoid unnecessary repeated processing when the underlying website content has not changed.
Available processing options depend on your subscription and enabled features.
Explore Site Workspace for more information about website content and processing workflows.
11. When Do Monthly Allowances Reset?
Monthly usage allowances follow your subscription billing cycle, not the calendar month.
The cycle begins on your subscription start date and renews each subscription month.
Example
If your subscription starts on September 15, your monthly usage period generally follows this schedule:
| Usage period | Starts | Next renewal |
|---|---|---|
| First month | September 15 | October 15 |
| Second month | October 15 | November 15 |
| Third month | November 15 | December 15 |
This means allowances do not necessarily reset on the first day of a calendar month.
Where applicable, the Dashboard displays the next reset date beneath the corresponding usage indicator.
Which Allowances Renew?
Recurring allowances include:
- Reports
- Domain changes
- Developer emails
- Support tickets
- API requests
- Processing jobs
Website and maximum-page allowances define the permitted capacity of your subscription instead of a monthly amount of consumable activity.
Unused recurring allowances should not be assumed to carry over into the following subscription month.
12. What Happens When You Approach a Limit?
The Usage card helps you recognize when a resource is approaching its allowance.
For example, a nearly full progress bar indicates that most of the permitted usage has already been consumed.
If you regularly approach a resource limit, review the activity responsible for that usage.
Recommended Actions
| Situation | What you can do |
|---|---|
| Page capacity is nearly reached | Review your website's page requirements and consider a plan with greater capacity |
| Report allowance is running low | Prioritize the reports you need before the next renewal |
| API usage is increasing | Review integration activity and request patterns |
| Few processing jobs remain | Avoid unnecessary regeneration or repeated manual processing |
| Domain changes are nearly exhausted | Confirm the intended domain before making additional changes |
| Developer email usage is high | Consolidate communications where practical |
| Support ticket usage is high | Review open issues and organize related questions before submitting additional requests |
When an allowance is exhausted, the corresponding operation may no longer be available until the allowance renews or your subscription provides additional capacity.
The exact behavior depends on the resource and your subscription configuration.
If your usage regularly exceeds the resources provided by your current plan, consider upgrading or discussing your requirements with SimplifyAccess.
13. Choosing the Right Plan
The most suitable subscription depends on the size of your website and how you intend to use SimplifyAccess.
Standard
The Standard Plan is designed for individual websites requiring core accessibility auditing and visitor accessibility tools.
It is a suitable starting point when your primary goal is to identify accessibility issues and provide visitor-facing assistance.
Pro
The Pro Plan adds more advanced workflows, including AI-assisted content features, media transcription, and deeper accessibility management capabilities.
It is intended for website owners and teams that want to go beyond core auditing.
Agency
The Agency Plan supports organizations and agencies managing multiple websites.
Each included controller maintains its own applicable resource allowances, while account-level resources such as support tickets remain shared.
Larger Requirements
Organizations with larger websites, higher processing requirements, or specialized infrastructure needs can explore additional solutions.
See Dedicated & Enterprise for more information.
Note: Always consult the current pricing page for the applicable numerical allowances and included features. Subscription details may change over time.
14. Frequently Asked Questions
Are resource limits shared between all my websites?
Most allowances apply separately to each controller or domain. Support tickets are shared across the entire account. The number of websites you can manage is determined by your subscription.
Do allowances reset on the first day of every month?
No. Monthly allowances follow your subscription cycle, beginning on your subscription start date.
Do unused API requests or jobs carry over?
Do not assume that unused monthly allowances carry over. The next subscription month provides a renewed allowance under your plan.
Does every website visitor count as one API request?
No. API usage is based on countable requests, not visitor numbers. A visitor may trigger several API requests or none, depending on the integration and features used.
What is the difference between API requests and jobs?
API requests involve supported API interactions, such as retrieving alternative content. Jobs are manually triggered processing operations, such as re-crawling content or generating reports.
Does generating a report use my Jobs allowance?
Report generation is among the manually triggered processing actions that may count toward the Jobs allowance, in addition to the report-generation quota.
Does my maximum page allowance reset every month?
No. Maximum Pages is a capacity limit associated with your controller, not a monthly consumption quota.
Are developer emails counted by recipient or by message?
Developer emails are counted as messages sent.
Do Agency customers receive separate support ticket allowances for every website?
No. Support tickets are counted per account and shared across all websites managed under that account.
Where can I find my current numerical limits?
Visit the pricing page for your subscription:
Make the most of your resources: Monitor your usage, understand which operations consume allowances, and choose a plan that matches your website's size and accessibility workflows.