Capabilities

What you can count on, whichever way we work together.

Watched like a user would

Accessibility as a floor, not a projectAccessibility is a level every page stands on, not a clean-up you repeat each year. This website is held to WCAG 2.1 level AA on every page, including the ones added since.
Checked in a real browserA page can pass every test and still be broken on screen. Your live pages are checked as your users see them, and visible breakage is reported to you with the page it occurs on.

Releases that put themselves backWhen a release misbehaves after it goes out, your users get the previous version back.
Broken releases repaired, not just revertedGoing back to the previous version is half the story. The fix follows, arriving in your repository as a change your team can read, and a working release goes out after it. Nobody has to file a ticket.
Releases your users never noticeNo maintenance page and no blank screen while a new version goes live. Your users keep working, and a release only counts as done once the running product shows it is the new version.

Your code, in your repositoryThe work lands in a code repository you own, and the code we build for you is yours. Changes arrive where your team already looks, in a form they can read.
Works in the stack you already haveYour product stays in the language, framework and style it is written in today. The work arrives inside your own codebase, and nothing is moved to other tools unless you say so.
Ask anything about your codebaseAsk a plain question about your product, such as what single sign-on would take, and get a written answer grounded in your own code. Nothing in the code is changed.

Progress you can followOne overview shows what is in progress, what is up next, what is waiting on you and what has shipped. A weekly summary and timely messages fill in the rest.

Within the access you grantYou decide which parts of your systems are open to the work, and the rest stay closed.
New package versions wait before they reach youA brand-new version of a third-party package does not go straight into your product. It waits 72 hours first, time in which a poisoned release can be reported and pulled.

Secrets never leave in a commitPasswords, keys and tokens are caught before they reach your repository, so your history stays clean and nothing needs rotating in a hurry.
Your users' requests, closed out with themBug reports and feedback from your product's own users become work on your product, and the person who reported a problem hears when its fix has shipped.
Your team, your rolesYou invite your own people as owner, admin or viewer, and you decide who can approve and who can only watch.
Your domain and certificate, kept currentYour product lives on your own domain over HTTPS, and certificate renewals happen without anyone setting a reminder.
Notifications where your team already isShipped changes and alerts post to the chat tool your team already reads, or to any webhook, so the news finds the people who need it.
Errors your users hit, gathered in one place and fixedWhen a page fails in a real user's browser, you see it on one page, grouped, with the versions it affects, and the error gets fixed.
Access keys you can limit and revokeYou decide how far each access key reaches. Limit a key to one product, and revoke it at any time.
A release counts only when it is runningA release is marked done only when your running product answers its health checks and runs the version that was shipped. Otherwise it goes back, and you are never told it is done.