DevOps Launchpad

A free training platform for all areas of Salesforce DevOps

Whether you're discovering Salesforce DevOps processes for the first time — or already have years of experience — DevOps Launchpad will help you:

Build your Salesforce DevOps skills
Free courses and articles on all things DevOps - from version control to backups.
Consolidate your knowledge
Fun quizzes to test your skills - from Git branching strategies to CI/CD automation.
Showcase your new expertise
Certifications and badges to add to your resume and share with your peers, colleagues.

Build your skills and expertise in all areas of Salesforce DevOps

An introduction to Salesforce development

Learn about the basics of developing and deploying on the customer success platform

Version control fundamentals

The basics of version control, how to get started, and when to consider a Git-based workflow

Git branching strategies

So you're ready to get started with version control - but how does it work in practice?

Salesforce backup

From why you need backups, to what your backup options are, this course is the perfect introduction

Gearset academy

Become a Gearset master with our guided training modules on the leading DevOps tool for Salesforce

Level up!

Earn badges, add qualified skills to your resume and get certificates to share with your peers.

DevOps Launchpad is a free training and learning platform for everyone in the Salesforce ecosystem.

It's filled with courses on all things DevOps - from source-driven development and DevOps automation - all the way through to in-depth technical articles from experts in their fields.

Complete courses, test your knowledge with quizzes and earn certificates to demonstrate your expertise to your colleagues and community peers.

Plot your course

Salesforce teams use such a mixed bag of tools and workflows that it can be easy to get lost when you're aiming for a mature DevOps process. Find out where you are on your DevOps journey, and where to go next!

Level 1:

Beginner

Change set riders typically work directly in production orgs, or in sandboxes with long periods between releases.

Level 2:

Novice

Git adopters pull ahead with a subset of metadata in version control to get familiar with the basics.

Level 3:

Practitioner

Rolling release pilots make Git their source of truth to unlock the benefits of DevOps, with better collaboration, debugging and auditing.

Level 4:

Expert

SFDX jetsetters take off with a whole raft of benefits with single-click releases based on automated deployments and testing.

Level 5:

Luminary

Pioneering package launchers add smart backups with quick restore times for data and metadata whenever accidental mistakes or disasters occur.

How DevOps improves your Salesforce release management process

Salesforce orgs can be hugely complex, needing a skilled team of admins, developers and release managers to keep them on track. When developing custom Salesforce features, it can be difficult to balance demands and resources within your team, hit release targets, and maintain a positive and productive culture — but DevOps can help. Changing your approach to releases can be daunting, but there are good reasons for you and your team to adopt DevOps practices.

Salesforce DevOps Fundamentals Certificate now available!

Salesforce DevOps is here to stay, and it’s never been more important to make sure you have the skills you need to be successful in a fast-changing world. That’s why we’re so excited to announce that our first certification track is now live on DevOps Launchpad! The Salesforce DevOps Fundamentals Certificate is the first certification program of its kind, providing a comprehensive, vendor-neutral foundation of Salesforce DevOps knowledge – and all at no charge.

What’s the difference between ‘source control’ and ‘version control’?

Tl;dr — Both terms are valid, but there are good reasons why ‘version control’ is used more often in the Salesforce world. Do you ever wonder which term you should use: ‘source control’ or ‘version control’? You might come across both, and they’re often used interchangeably. But are they the same thing? Is one more ‘correct’ than the other? Does it depend on the context?