Plans and pricing
Tidewater CI builds, tests and ships your code from the same pipeline file, on our runners or on yours. Pick the plan that matches how your organisation works today; you can move between plans at the end of any billing period.
Prices are loaded at runtime; contact sales for a quote.
What every plan includes
- Unlimited public and private projects.
- Pipelines as code, with reusable templates and a visual editor.
- Build caches shared between branches, with a manual purge button.
- Secrets stored encrypted and scoped to an environment.
- Status badges, commit checks and merge gates for the main code hosts.
- A command line client for Linux, macOS and Windows.
Both plans run on the same infrastructure. The differences are in the limits, in how long we keep your history and in the ways you can reach us when something goes wrong.
Compare plans
The table lists the limits that differ between the two plans. A dash means the feature is not part of the plan.
| Feature | Standard | Enterprise |
|---|---|---|
| Custom domains | 1–5 | 1–3 per region |
| Storage per workspace | 50 GB | 2 TB |
| API requests per minute | 600 | 6 000 |
| Concurrent pipelines | 4 | 40 |
| Audit log retention | 30 days | 365 days |
| Build artifact retention | 14 days | 180 days |
| Single sign-on (SAML) | — | Included |
| Self-hosted runner | — | Available on request |
| Support | Email, 2 business days | 24/7 phone and email |
Limits are counted per workspace unless the row says otherwise.
How the limits work
Storage
Storage covers build caches, artifacts and container layers. When a workspace reaches its limit, the oldest caches are removed first; artifacts are never deleted before their retention period ends. You can see the current usage on the workspace settings page, and an owner receives a notice when usage passes four fifths of the limit.
Pipelines
A pipeline counts as concurrent from the moment its first job starts until its last job ends. Pipelines above the limit wait in a queue in the order they were created. Manual jobs that are waiting for approval do not count.
API
The request limit applies to each access token. Requests above the limit receive a 429 response with a header that says when to retry. Webhook deliveries that we send to you are not counted.
Domains
A custom domain lets you serve build previews and documentation sites from an address of your own. Certificates are issued and renewed for you. On Enterprise the limit is counted separately in each region where the workspace has runners.
Moving from another service
An importer reads the pipeline files of the most common build services and writes the equivalent Tidewater file next to them, with a comment on every step it could not translate. Nothing is changed in your repository until you open the pull request it prepares.
Secrets are never imported. The importer lists the names it found so that you can create them again by hand, and it marks the jobs that will fail until you do.
Build history stays in the service you are leaving. If you need it for an audit, export it there first; we can attach the archive to your workspace as a read-only record.
Frequently asked questions
Can I try Enterprise before I decide?
Yes. Ask sales for a trial workspace; it stays active for three weeks and keeps the pipelines you create if you subscribe afterwards.
Do you offer discounts?
Registered charities, schools and open source projects with a public repository can apply for a reduced rate. The form is on the contact page.
How do I pay?
Standard is paid by card. Enterprise can also be paid by bank transfer against an invoice, with payment terms agreed in the contract.
Where is my data stored?
You choose the region when you create the workspace. Build logs and artifacts stay in that region; account data is stored in the region of the organisation's owner.
What happens if I cancel?
The workspace becomes read-only at the end of the billing period. You can export pipelines, logs and artifacts during the following month; after that they are deleted.