Signadot Pricing
How pricing works
Test Invocations are billed each time you run your complete test suite in any Sandbox, regardless of suite size, whether that's E2E tests, integration tests, or SmartTests.
We track concurrent devboxes. A devbox is either a local workstation or a Cloud Development Environment (CDE) that integrates with Sandboxes.
Starter
Business
Enterprise
"Signadot for the preview environments use case fit what we were trying to do better than anything else. It was a more mature solution than the other stuff that we were looking at. And the return on the investment was obvious... just in infrastructure costs, it saves us about $2 million annually."
"Our vision when we started talking to Signadot was that we wanted to have the same stack for testing and production. Signadot has allowed us to do just that, bringing down the lead time for our developers to test changes from 30 minutes to literally 60 seconds."
Savings calculators
Calculate developer time saved from faster cycles with local and PR testing vs. post-merge cycles involving slow CI/staging.
Assumes 48 weeks in a year
Calculate cost savings from lightweight Sandboxes vs. full environment duplication.
Costs when duplicating environments for each developer = #devs x #services x resource per service
Costs with Sandboxes = (#devs + #services) x resource per service
Calculate savings from catching integration bugs before they reach staging and production.
Estimated costs: Staging bugs $1,500 each, production incidents $10,000 each.
How teams use Signadot
AI coding agents and developers use Signadot to validate code changes rapidly in production-like environments.
Ad-hoc Testing for Agents & Developers
Coding agents and developers spin up lightweight sandboxes to test changes instantly — no shared staging environment needed.
Automated Testing Pre-merge
Run API tests, end-to-end tests, and integration tests in isolated sandboxes on every pull request. Debug issues by inspecting API traffic and cluster data.
Frequently asked questions
The Signadot operator runs securely in your Kubernetes cluster. The Signadot Dashboard and API are hosted in our cloud which runs in AWS.
Our pricing is usage-based: you pay for Sandboxes created, Test Invocations, and Concurrent Local Connections. Running signadot job submit or signadot smart-test run counts as one Test Invocation, regardless of how many individual tests execute. You can track your usage in real-time through the dashboard.
Test Invocations are a suite of automated tests run by the Signadot operator to compare the behavior of Sandboxed and baseline Microservices. For example, Test Invocations can automatically detect API regressions in Pull Requests using AI models that continuously learn the baseline behavior.
Start with your monthly pull request volume, but remember you control which PRs get Sandboxes - not every PR needs one. For Test Invocations, it depends on your testing frequency: if you run tests once per PR, expect roughly 1x your Sandbox count. If you run tests on every commit, expect 3-5x your Sandbox count since PRs typically have multiple commits. Concurrent local connections can be estimated at ~ 70-100% of users.
For the Business Plan you can pay by credit card or ACH. Please contact us for flexible payment options for the Enterprise plan.
Sandboxes represent shadow deployments of Microservices associated with a routing key. Sandboxes enable isolated testing of branch versions of Microservices via selective routing of test traffic.
Yes! We offer a 30 day free trial of the Business plan. The Starter plan is free forever.
We follow the best practices around privacy and security. Signadot is SOC 2 Type 2 certified. All data at rest is encrypted and TLS used for network communication.
We offer Professional Services to help with various tasks like Installation & Configuration, CI integration, OpenTelemetry instrumentation and much more. Email us at info@signadot.com to learn more.
