Self-Service Delivery removes the friction of having to request an environment for a project, or the toil of setting up the delivery process yourself. It puts the entire delivery process in front of you, so that you always have visibility and control. The information and tools necessary to ship great software are right at your fingertips, enabling you to start new projects, develop and have those projects delivered automatically.
Delivery is more than the act of building, testing and deploying. Delivery is everything you do in order to ship, including creating new projects, updating dependencies, refactoring code and countless more tasks. Self-Service Delivery means that you can develop and automate your own tasks, to scratch your own itches.
Atomist is a platform for developing Self-Service Delivery for your team.
Atomist enables automatic delivery across all your projects. Evolve that flow in one place, not repository by repository. Enabled by the Software Delivery Machine’s event-driven approach, delivery is consistent and automatic across all projects.
All activity across the delivery flow, from initial commit through promotion and verification in production, is visible in one place. Always know the state of delivery for your projects. Take direct action when needed in chat or by issuing commands.
Use virtually any repository as a starter. Easily start from known good code bases, whether one in our list, a popular repository on GitHub, or one of your own. Creation is a snap: Atomist creates a new repository for you, and the project is automatically deliverable from the initial commit.
Easy one-time setup to deploy to Kubernetes whether you use Minikube, Google Kubernetes Engine, Azure Kubernetes Service, Amazon Elastic Kubernetes Service, RedHat OpenShift, Pivotal Container Service or open source Kubernetes.
Chat-native interface makes your delivery process part of the conversation in Slack or Microsoft Teams. See delivery progress in chat and take action immediately, by merging a pull request, assigning an issue, or approving a deployment. Atomist bot commands make it easy to create projects or initiate a deployment.
When you need to change how delivery works – for example, to add vulnerability scanning, push Docker images to a different artifact store, or add your own bot commands – the delivery process is completely programmable. We think code speaks louder than YAML.
Enabling Self-Service Delivery requires support to put control in the hands of the developer, and the engine to intelligently automate the delivery process. The heart of Atomist is the Software Delivery Machine (SDM). It’s an event-driven delivery automation engine that maintains a rich model of your app and delivery flow and is fully programmable in code.
Giving direct control to take actions like creating a new project or approving a deployment helps teams ship faster. Atomist has a rich command framework for you to create custom commands that are available to everyone in chat or via command-line. Commands can be attached to chat notifications so that users can take action right there – promote that staging deployment.
Put complete visibility into the delivery flow in front of everyone in your team with correlated and actionable notifications directly in chat. Notifications keep everyone up to speed. Native chatops with bot support in Slack and Microsoft Teams means better team alignment and collaboration.
Atomist is an event-driven delivery platform that captures events from all stages of development delivery, correlates events to track the flow of activity, triggers automation action from any event, and logs activity acting as an audit trail.
Cortex is a model of correlated events and information related to a project, stored in a graph database, queryable for reporting and use in commands and notifications.
Bi-directional integration with third-party tools used in your development and delivery flow means Atomist receives events, and also integrates with those tools APIs to directly execute delivery stages.
Two new terms have recently emerged around software delivery: Software Defined Delivery and Progressive Delivery. Why? How do they relate to Continuous Delivery? Several forces today make delivery increasingly complex. Notably, proliferation of repositories, with hundreds of small projects replacing a handful of monoliths; desire for greater automation to realize the full potential of CD across multiple environments; the rise of feature flagging; and increased evidence (such as the Equifax debacle)
Atomist co-founder and Chief Architect, Jim Clark, recently sat in with Rob Hirschfeld for an episode of the L8ist Sh9y Podcast. It's a wide-ranging conversation about delivery as workflow, event-driven delivery, code analysis, GraphQL and ChatOps.
My co-founder, Rod Johnson recently talked with Gene Kim, (see “The Phoenix Project” and “The DevOps Handbook”), and Alex Williams of The New Stack on The Makers podcast.
The other day I heard a sad story about a build that was broken for weeks due to a bug introduced in an open-source library. It took the maintainer a long time to fix it (they're not getting paid for this, no criticism). In the enterprise they had so many layers of repository caching the team couldn't escape the buggy version. Even sadder, that library existed for fancy terminal output of a library that produced documentation (typedoc). A nonessential feature of a nonessential build step blocked
Lorem ipsum dolor sit amet consectetur adipisicing elit. Vitae aliquam odio molestias doloribus consequuntur ipsa labore ab consectetur suscipit esse est quam, enim doloremque facere maxime velit error, ducimus temporibus. Lorem, ipsum dolor sit amet consectetur adipisicing elit. Ea commodi omnis reprehenderit quod aliquam natus autem facilis officiis? At est exercitationem quibusdam doloribus magni iste suscipit, voluptatibus iusto esse accusantium ea excepturi voluptas illo, quasi, numquam dolores explicabo nihil sit!
Go from brand new project to deployed in minutes.
The team will reply as soon as they can
Interested in evaluating Atomist? Request a demo meeting with us