A stack of thin flat layers seen at an angle, the top layers tinted red. AI-generated image
Development

The Stack Behind a 22-Plugin IDE Business

By Paul Piper 2 min read

People ask me what it takes to run 22 JetBrains plugins, two iOS apps, and a handful of web products with a small team. The answer is the right tools and a stubborn refusal to use more than necessary.

Plugins and distribution

IntelliJ Platform SDK with Kotlin and Java. Every one of our 22 plugins runs on this. Kotlin for new code, Java for the older plugins that started before we switched. The platform is powerful and maybe 30% documented, so you learn the rest by reading the IntelliJ Community Edition source.

Gradle for builds. The IntelliJ Platform Gradle Plugin handles most of the IDE-specific wiring. I used to fight with it. Now it mostly works.

GitHub Actions for CI. When a change lands, CI runs the tests per plugin across IDE versions. A release build publishes to the JetBrains Marketplace automatically. I tried Jenkins years ago. GitHub Actions is simpler and I do not have to maintain a server.

JetBrains Marketplace for distribution, billing, licensing, and trial management. They take a cut, and it is worth it. I do not want to build a license server.

Web and iOS

Hugo for our websites: ilscipio.com, getslaide.com, getkronk.com. Static sites. Fast, cheap to host, nothing to maintain. I considered Next.js and decided I did not need a JavaScript framework to serve marketing pages.

Stripe for web product payments. Slaide Pro and Slaide Hosted run through Stripe. The API is good. The dashboard is good. I have no complaints.

SwiftUI for Yarn Squirrel (Jenni’s knitting app) and Slaide for iOS. Xcode is non-negotiable on that side.

What I use and what I do not

Claude Code for development assistance. I use it daily for everything from plugin code to website updates. It handles the mechanical parts so I can focus on architecture and the parts that need judgment. Git with GitHub. Nothing exotic.

No Kubernetes. No microservices. No feature flags. No monitoring stack beyond what Docker logs give me. This stack does not scale to a 50-person team, and I know that. It scales to me and a few collaborators, and that is who it needs to serve.