Kodmos
Get started
Docs / Changelog

Changelog

What’s new in Kodmos

  1. Rollbacks, approvals and why it failed

    • One-click rollback: an event’s projects go back to what was live before it, last step first, as a deploy you can watch.
    • Gate steps on Business: approvals by the people you name, soak time, and health checks between deployments.
    • A failed deployment shows the last lines of its log, in its panel and its email, with an optional summary by Claude.

  2. Kodmos, open to your tools

    • API tokens for CI and scripts, each with a role and only the permissions it needs; CI can answer for its repository once its tests pass.
    • Comments on pull requests: where and when each one deploys, and where it is live once it has.
    • A sandbox to try Kodmos without connecting GitHub.
    • Kodmos on a personal GitHub account, and a move to an organization later without losing anything.
    • Team and Business on GitHub Marketplace, paid on your GitHub bill.

  3. Release days that run themselves

    • Release trains: a release that repeats every week plans its own events, numbered, a few days ahead; skip or move one occurrence.
    • Slack: each team’s channel follows its events and deploys, reminders come as direct messages you answer with a button, and DevOps can deploy from Slack.
    • Needs you: an inbox in the header with the branches you owe, events ready to deploy, failed deployments and access requests, and what you were told lately.
    • Calendar feeds: your releases, your organization’s or a team’s in Google Calendar, Outlook or Apple Calendar.
    • Deploys show the time left on each deployment, and when the whole deploy should be done.

  4. What deploys, and what is live

    • Release notes: each project’s new commits and pull requests since what is live, before a deploy, on each deploy, and in its email.
    • A Live page: every repository by environment, what deployed it, how far behind its default branch it is, and whether a commit or pull request is live yet.
    • Answers show their commit’s checks, and locking or deploying with failing checks asks first.
    • Answer in one click with the event’s release branch, or the branch a project deployed from last time.

  5. Paid plans

    • Owners can choose Team or Business, monthly or yearly, and pay by card through Stripe.
    • Extra repositories are billed as you add them, prorated, and credited when you archive flows.
    • Cards, invoices and cancelling are in Stripe’s portal; a failed payment gives you a week to fix it.

  6. Pinned releases, release tags and history that stays

    • Locking an event pins each project to its branch’s newest commit; a push after the lock stops the deploy until DevOps re-pins it.
    • Release tags: a deploy runs each project on a tag at exactly the commit the event locked.
    • Emails show every time in the reader’s timezone, and organizations plan in their own.
    • Emails that cannot be sent are tried again for half an hour, and DevOps see when they fail.
    • Every deployment is kept in a deploy history, and old runs keep their summary.
    • Flow versions you can restore, and archiving a flow instead of deleting it.
    • An audit log of who did what, with a CSV export.
    • Plans and pricing, account deletion, and the privacy, terms and security pages.

  7. Use-case guides, in four languages

    • Guides to planning releases across GitHub repositories.
    • Kodmos now speaks English, Spanish, Albanian and Turkish.

  8. Kodmos

    • Deployment events, flows that chain GitHub Actions across repositories, a live monitor, and email for everyone involved.