June 15, 2026
Plugin panic meets vibe coding
Building a plugin system without runtime, storage, or shared JavaScript context
Startup boss admits he feared this feature would ‘eat the team alive’ — commenters are hooked
TLDR: Tolgee built a new way to test custom add-ons fast without risking its main product, and the founder says he did the first version shockingly quickly with artificial intelligence help. Commenters are locked onto the real drama: his candid admission that he feared this feature would become a team-destroying nightmare.
Tolgee’s founder just dropped a behind-the-scenes confession that reads less like a dry product update and more like a founder panic diary. The company wanted a way to test new ideas quickly for individual customers without messing with its main app, which is stable but slow to change. So instead of stuffing every experiment into the core product, Tolgee built a plugin-style add-on system where outside tools can plug in through isolated little windows and limited access. In plain English: faster experiments, less chance of breaking the main thing.
But the real star here is the mood in the comments. Founder Jan Cizmar openly admitted he’d been scared to build this for ages because every path seemed to lead to endless cleanup, security worries, and a giant engineering time sink. That quote — the feature could have “eat the team alive” — is the kind of brutally honest line internet people love. It turns a technical architecture post into a mini-drama about fear, restraint, and finally just doing the thing.
There’s also a juicy side plot: Jan says the proof-of-concept was basically “vibe-coded” with artificial intelligence help in about three days, but insists it’s not going straight into production. That’s exactly the kind of sentence that makes comment sections perk up: half impressed by the speed, half waiting to ask if this is genius or chaos. The overall reaction feels like a mix of “wow, clever workaround”, “finally, someone said plugin systems are terrifying”, and a little bit of classic developer humor: if the system avoids becoming a monster, everybody wins.
Key Points
- •Tolgee created Tolgee Apps to enable faster experimentation and customer-specific extensions without changing the core platform.
- •The core Tolgee platform is built with Spring Boot and TypeScript/React and follows a stable, heavily tested release process.
- •Tolgee Apps are defined by a JSON manifest that specifies metadata, UI modules, scopes, webhook subscriptions, and an optional decorators endpoint.
- •UI modules are rendered in sandboxed iframes, receive scoped context via postMessage, and can access the Tolgee REST API using short-lived JWT tokens.
- •The article includes a sample Back Translate app manifest showing scopes, webhook events, and UI extension points such as a tools panel and translation action panel.