r/platform_engineering
We built internal "lovable" on Backstage + EKS where non-engineers ship apps with Claude securely
- upvotes
- 4
- comments
- 3
Post
Sharing this because I have not seen a lot posted about solutions to this problem. We are a freight-data SaaS - always a lot of internal demand for dashboards and whatnot. I'm VP R&D and also responsible for Cyber. Once we opened the AI door, people outside tech started building stuff left and right. Everyone started dragging in Lovable or Replit apps asking to connect them to our data. We tried pushing people into a vendor solution for low-code internal tool builder - ended up way too manual, no AI builder at the time. Tried pushing people into BI - same manual build issue, and useless as soon as you need something off the standard functionality. What we built in the end Backstage as the portal with one scaffolder template. Asks for app name, makes GitHub repo with Jenkins pipeline, infra, SSO auth, live URL. Takes a few seconds. Claude Code skills shipped as a plugin in the repo. The author describes what they need and Claude already knows our conventions + the important infra points for the app platform. Vibe vibe, push, app updates and live in a few minutes. This experience is what made it stick with non-tech people. One EKS cluster, dev/prod as namespaces, Karpenter for nodes. Started on ECS with one ALB + Terraform stack per app. Worked at 10 apps, started being annoying and slow and expensive at 50+. Auth at the ALB, not in the app. VPN → internal ALB → Cognito...
Keep reading with a free account
The rest of this post, and every signal for Jumpcloud, is in your free account.
Extracted from these lines
VPN → internal ALB → Cognito → SAML to JumpCloud. ALB sets the cookie, forwards with identity headers.
From the post
Access via JumpCloud group or named emails + VPN required.
From the post