Pliow: SDK and runtime for dynamic software interfaces

Hi Product Hunters 👋 Lorenzo and Emanuele here, we're the two people building Pliow. Pliow is the SDK and runtime for dynamic software interfaces: install it once, and every user of your web app gets their own interface, generated on your existing codebase. 🚨 The problem we're solving Software has always been one-size-fits-all. A sales rep and an ops lead open the exact same screen, even though their jobs share almost nothing. Every "can you customize this for us" request turns into an engineering ticket. Half of it is too account-specific to ever go in the core product, so it rots as tech debt nobody owns. The only real fix today is a forward deployed engineer, someone who sits inside one customer and rebuilds the product by hand, for $150K–$500K a year. Only the biggest accounts ever get it. 🥁 What you get 1️⃣ Pliow SDK: a few lines in your existing product. No rewrite, no migration, no second product to maintain. 2️⃣ Verified runtime: every generated component is compiled, policy-checked and render-tested, then runs in an isolated per-user sandbox. Your shared codebase is never modified. 3️⃣ Full-stack reach: React on the frontend, your backend logic, and an agent harness, so a request can reach into the middleware, not just restyle the page. 4️⃣ Per-user versioning: every change is versioned, audited and reversible. 🏰 Our story We kept watching the same scene in enterprise software: a customer says "this is great, but we'd love it if it worked like this for our team," and an engineer gets sent in to rebuild that slice of the product by hand, for that one account. It works, and almost nobody can afford it. We wanted to know if an agent could do it for every user instead. YC's request for startups on Dynamic Software Interfaces argues the same: coding agents are finally good enough for users to become their own forward deployed engineers. ❓ Why Pliow Other tools generate UI at build time for developers, or bolt a chat layer onto your product. Pliow regenerates the interface itself, per end user, at runtime, on an app already in production. You ship your shared primitives; each user gets their own interface on top, either by asking or learned from how they work. 🚀 Special launch offer We're onboarding a small group of B2B SaaS teams as design partners: free early access and direct support from us. Live demo (no signup) 👉 https://pliow.com/demo Video demo 👉 https://youtu.be/54ZxSeLnUuQ We'd love your honest feedback, most of all where you think this breaks or where it wouldn't fit 💬

Framer AI AgentsDesign and publish professional sites with AI

Promoted

Maker

📌

1d ago

The dynamic interface idea is genuinely interesting for B2B workflows where roles vary so much. One concrete suggestion: add a diff or preview mode so admins can see exactly what a generated interface will look like for a specific user before it goes live. That kind of "show me what Sarah in accounting sees" view would make rollout way less scary for ops teams worried about breaking things.

2h ago