Website testing for agencies

What an agency needs, and where it is

• A workspace for each client. A workspace is a normal SpinUI organization with its own suites, tests, runs, results, secrets and people. Nothing is shared between workspaces. Team and Business. Client workspaces.
• One bill. Workspaces are billed to the agency account. There is one subscription, and SpinUI does not invoice your clients.
• Per-client separation. A person sees a workspace only if they are a member of it, so a client’s people see their own workspace and nothing of your other clients. Creating a workspace and adding yourself to one are written to the audit trail of both organizations.
• Schedules and alerts for each client. Each workspace has its own schedules and alert destinations, so a failure at one client goes to the people for that client. Email, Slack, Microsoft Teams and signed webhooks are available. Slack and webhook alerts: Individual and up. Teams alerts: Team and Business. Schedules and alerts.
• Private runners for client intranets. For a staging site behind a VPN or an intranet, install a runner inside that network. It only connects out, over HTTPS, and a runner works for one organization only. Private runners: Team and Business. Cloud and private runners.
• A run after every deploy. A trigger URL starts one suite when your deploy script, or WordPress after a plugin update, sends it an HTTP POST. Repeated calls while a run is waiting or running give that one run. Trigger URLs and CI tokens: Individual and up. MCP for coding agents: Team and Business. Pipelines and coding agents.
• Tests without code. Record a test in Chrome by using the client’s site. Chrome test recorder.
• Something to send the client. Every run has a report you can open and download as a PDF. An Admin can also turn on public links, which are off by default.

How pricing works for agencies

Client workspaces come with the plan, not as a separate add-on. This is how many each plan allows:

Plan	Client workspaces	Users
Free	No client workspaces	1 user
Individual	No client workspaces	1 user
Team	Up to 3 client workspaces	5 users
Business	Up to 25 client workspaces	20 users

• Shared, not multiplied. Your agency and its workspaces share one set of allowances: cloud minutes, tests at once, the AI allowance and the allowance of received test emails. Adding a workspace does not add minutes.
• Limits count the whole account. Users, suites, schedules, trigger URLs and CI tokens are counted across the agency and all its workspaces. A person who is a member of several of your workspaces uses one user place, and so does a pending invitation. People you invite from a client count too.
• Private runners do not use cloud minutes. Runs on a runner inside a client’s network are not counted against the included cloud minutes.
• No overage fees. When the minutes are used up, new cloud work waits until they reset or you upgrade. Work already running finishes.
• Where to see the numbers. The pricing page has every plan’s limits side by side.

How an agency gets started

Client workspaces are switched on for an agency account by the SpinUI team, and the number you can create follows your plan. Accounts are opened on request for now. Contact us and say which plan you need and how many clients you work with. When the account is ready, you create each client’s workspace yourself under Settings, Client workspaces.

What is not there

• Workspaces go one level deep. A client workspace cannot create workspaces of its own.
• SpinUI does not offer custom branding for client reports. Reports carry SpinUI’s name.
• SpinUI bills the agency only. It does not split a bill between your clients.

Read more: all features, security and data handling, pricing.