Straight answers.

No. Single sign-on means your people log in to every tool through one identity provider. SmashSSO does not sit in the login path: everyone keeps logging in to each tool the way they do now. What it replaces is the reason most small companies want SSO in the first place, which is adding and removing people in one place. If you need enforced login through an identity provider, for example for a compliance audit that names SAML, you need real SSO and this is not it.

Because for a company of 5 to 50 people, the job SSO gets bought for is onboarding and offboarding. SmashSSO does that job for a flat fee instead of an Enterprise upgrade on every tool.

The owner or operations lead of a small business, up to about 50 people, running somewhere between 10 and 50 tools on Google Workspace, who is currently the person doing invites by hand.

No. Only admins sign in to SmashSSO. Everyone else is a record that comes from your Google Workspace directory.

An AI model driving a real browser. It opens the tool's admin page, reads the screen, and clicks and types its way through the same steps you would. We use it for tools that have no member API on your plan.

You log in once to each tool in a browser we host and stream to you, using your own admin account or a dedicated one you have set up with access to that tool. We then store the session the tool issued, encrypted. Your password and 2FA codes are typed into the tool itself and are not stored by us. Details on the security page.

Whichever account you logged in with when you connected the tool. Use your own admin account and changes are recorded as made by you. Create a dedicated admin account for SmashSSO, log in with that instead, and they are recorded under it, which keeps agent activity separate from yours. Either way, SmashSSO keeps its own log of which admin requested each change and what the agent did.

The tool is flagged, its pending runs wait, and you get an email. Log in again through the live browser and the runs continue. Some tools expire sessions often; those will ask more often.

It is built not to. If a step would add a paid seat or touch billing, the run pauses and asks for your approval. You should still know that this depends on the agent recognising such a step; it is a strong safeguard, not a mathematical guarantee.

API connectors are as reliable as the API. UI agents are slower and can fail when a tool changes its screens or challenges the browser. A failed run tells you it failed and shows its last screenshot; it does not report success it cannot confirm.

No. Tools with aggressive bot detection, including some cloud consoles and financial dashboards, may block an automated browser. Those can be tracked by hand instead. The tools page says how each one is handled.

It varies. Some tools' terms of service restrict automated or scripted use of their interface. You are acting on your own account with your own admin rights, but you are responsible for checking the terms of the tools you connect. Where a tool offers a member API on your plan, we use that instead.

It is a real risk and you should weigh it. An admin session is powerful, and you would be trusting us to hold it. A dedicated account with only the rights needed to manage members limits what that session can do. We encrypt sessions at rest, use each one only for runs you request, and limit what the agent may do. The security page describes this without the gloss.

A flat fee for the whole company: $499 a month billed monthly, $399 quarterly, $299 every six months, or $199 billed annually. No per-seat or per-tool charges. See pricing.

No. There is a 30-day money-back guarantee instead: if it does not do what we say, email us within 30 days for a full refund.

From each vendor's public pricing page, with the source linked on every row and the date we read it. Vendors change prices, so treat the calculator as an estimate and check the source.