AEM Rapid Launcher

[#1]

AEM Rapid Launcher

  by Santosh Sai

Overview

Hi AEM developers 👋,

I’m excited to share AEM Rapid Launcher, a lightweight Python-based GUI tool I’ve built to streamline local AEM project workflows — including launching Author/Publish instances, module deployments, Git-based project setup, and more.

🧰 Key Features:

• Start/stop AEM instances with a single click

• Deploy individual modules or full builds with profile support

• View and filter logs in real-time

• Clone/import AEM projects from Git

• Tabbed interface for Author, Publish, Dispatcher, and Config management
  
  

🌐 Read the full story & setup guide in my latest blog:
🔗 https://techinnovia.com/simplifying-aem-local-development-with-aem-rapid-launcher/

📦 Open Source on GitHub:
🔗 https://github.com/github-santosh-sai/aem-rapid-launcher

💬 I’d love your feedback, suggestions, and contributions. Let’s make local AEM development faster and more delightful!

 

Q&A

Please use this thread to ask questions relating to this article

[#2]

Thanks @SantoshSai  - This is very useful - specially new devs who onboarding to projects.

[#3]

@SantoshSai Thanks Santosh for sharing this, looks super handy. I really like how you’ve bundled start/stop, deployments, and log viewing into one lightweight tool; it feels like it can cut down setup friction. Quick question: does AEM Rapid Launcher also support handling multiple projects/configurations (say switching between different client codebases), or is it currently optimized for a single project at a time? Curious how you’re envisioning that in real-world workflows...

[#4]

Hi @kautuk_sahni, thanks a lot for the feedback!

Yes - AEM Rapid Launcher does support multiple projects/configurations. You can clone or import multiple projects into the aem_projects/ directory, and each one maintains its own configuration. From the Project Configuration tab, you can switch between projects and handle builds, selective module deployments, and instance management independently - so it works smoothly across different client codebases.

The goal is to keep the tool lightweight while still flexible enough for real-world workflows where you might juggle multiple projects at once. I’ll also continue refining the UX so that switching between projects becomes even more seamless.

If you have a specific workflow or scenario in mind, I’d love to hear it - that really helps shape the roadmap!