Free on five repos.
Priced by repo past that.
Install the app on GitHub and it is free on up to five adopted repos, with every feature except the required second approver, which Team and Team Plus add. On every plan, deploys run in your own GitHub Actions.
- Previews and deploys run in your own runners, with your own credentials. Sluiceway never holds a cloud credential, in any tier.
- The issue is a view, never the source of truth. Before every deploy the stack is previewed again, and nothing happens unless the fresh preview still matches what was ticked.
- No property value reaches the dashboard unless the repo lists the path. No telemetry from the action.
- The hosted app keeps stack-level facts only: state, counts, who ticked, which commit, when. Never resource names, property paths, diffs or values.
- Sluiceway cannot cause a deploy by itself. A person ticks, the same rule judges every tick, the fresh preview and the hash check stand, and a destroy waits for a person.
These hold on every plan, and in the action run on its own.
The app's plans
Every feature except the required second approver, on up to five adopted repos, for good.
- The onboarding pull request that sets up the action
- Ticks picked up within about a second
- The console and the org view across every repo
- Tick from the console and the command line
- The audit log and Insights
- Edit mode, saved as a pull request
Up to 25 adopted repos, and 13 months of audit history.
- Every feature of Free
- A required second approver
- Up to 25 adopted repos
- 13 months of audit history, with the CSV export
Up to 100 adopted repos, and 3 years of audit history.
- Every feature of Free
- A required second approver
- Up to 100 adopted repos
- 3 years of audit history, with the CSV export
More than 100 adopted repos
Talk to us at [email protected]. A plan agreed in writing is paid by invoice, and any plan can be.
Prices are in US dollars and exclude VAT, which is added where the law requires.
Or run the action yourself
Shipped 0.50.0Every plan above runs this action. On its own it makes the same deploys, with the issue as the only dashboard: open source, Apache-2.0, free and complete in as many repos as you add it to. It is in beta, released as 0.x. Nothing about deploying changes at any plan's line. How the app and the action work together.
- Pulumi, OpenTofu and Terraform, Helm, and Kubernetes manifests
- One issue, one row per stack, tick to deploy
- A preview page per pending stack, and a check on every pull request
- Merge and deploy, stack dependencies, and drift, opt-in
- A kill switch that stops every deploy, a rehearsal that runs a tick without deploying, ignored stacks, read-only mode
- Notifications, opt-in: Slack, Telegram or your own webhook
What you get, line by line
A plan sets how many adopted repos the app shows whole and how far back the audit log goes. The free plan has every feature except the required second approver, which Team and Team Plus add.
| What you get | Free | Team | Team Plus |
|---|---|---|---|
| Every plan keeps | |||
| Deploys run in your own runners | Yes | Yes | Yes |
| Sluiceway holds a cloud credential | Never | Never | Never |
| Fresh preview, compared with what was ticked, before every deploy | Yes | Yes | Yes |
| What the app keeps | Stack-level facts | Stack-level facts | Stack-level facts |
| What a plan sets | |||
| Adopted repos | Up to 5 | Up to 25 | Up to 100 |
| Audit history | 30 days | 13 months | 3 years |
| Price a month | 0 | 199 USD | 499 USD |
| Price a year | 0 | 1,990 USD | 4,990 USD |
| Repos the app is installed on without a dashboard | Never counted | Never counted | Never counted |
| The app | |||
| The app picks a tick on the issue up within about a second, on a repo whose sluiceway.yaml names the app, with the action's resolve as the fallback | Yes | Yes | Yes |
| The org view: every stack of every repo, grouped by what needs a person | Yes | Yes | Yes |
| The audit log, with deploys made outside the dashboard, and its CSV export | Yes | Yes | Yes |
| Tick and rescan from the console and the command line, on a repo whose sluiceway.yaml names the app | Yes | Yes | Yes |
| Insights: lead time from merge to deploy, deploys per week, change failure rate | Yes | Yes | Yes |
| Edit mode: change the dashboard, saved as a pull request | Yes | Yes | Yes |
| The onboarding pull request for a repo without a dashboard | Yes | Yes | Yes |
| A required second approver: GitHub holds the deploy job until a second person, not the ticker, approves in the app | No | Yes | Yes |
| The action | |||
| The dashboard issue, tick to deploy, on every repo | Yes | Yes | Yes |
| Deploys on adopted repos past the plan's line | Unchanged | Unchanged | Unchanged |
An adopted repo is a repo with a dashboard
The action has run a scan there. A repo the app is installed on without a dashboard never counts, so installing the app on a whole org costs nothing.
The second approver is a GitHub deployment protection rule
GitHub offers that rule on GitHub Enterprise, and on public repos on every GitHub plan. Private repos below GitHub Enterprise cannot use it. On Free every held job is approved at once, so no deploy waits.
Past the line, nothing about deploying changes
You choose which adopted repos are active in the app's Settings; the default is the busiest. An adopted repo past the line is listed greyed out, with its name and state counts only. The action keeps deploying on every repo, with or without the app, and the dashboard on GitHub works as always.
How paying works
An admin of the org picks Team or Team Plus in the app and pays by card through Stripe, monthly or yearly. Stripe's customer portal changes or cancels the plan, and a monthly plan cancels any time.
There is no trial: the free plan is every feature but the required second approver, on five adopted repos, for good. To pay by invoice, write to [email protected].
Next in the app
Planned- Planned: GitHub teams in who may tick
No date is set.