Ployin
Around.
An honest teardown of Ploy — researched, written, and shipped on Ploy itself. I used it to build real websites, watched the agents work, and wrote down everything that wowed me and everything I'd fix.
I ran Ploy on my own websites, let the agents ship real pages, then turned my customer experience into this site.
Hit spin. See what I've built.
28 things · 0 pulls
Press the button →
Where Ploy genuinely wowed me.
Each note has a screenshot from real usage — click any thumbnail to expand it.
It found trends I'd actually used
From nothing but my site's context, Ploy surfaced marketing angles that aligned with my product — some I'd already tried myself. That it inferred them cold was genuinely surprising.
It understood the offer deeply
It grasped what I was selling and why it mattered, then built a page that explained my competitive advantage more clearly than my own copy did.
Publishing was painless — and responsive
One click to ship, and it resized cleanly across screen sizes without me babysitting breakpoints.
It coached me on SEO
Indexable URLs, concrete on-page suggestions, and a clean export I could pipe straight into Codex. Real help for a beginner, not vague advice.
The rough edges I hit.
Written the way I'd file them on the team — specific, reproducible, and ranked by how much they got in my way. Click any thumbnail to expand the screenshot.
It couldn't see the embedded YouTube demo
On hephasbot.com, Ploy missed the embedded YouTube clip entirely and suggested I add a video instead of recognizing the one already there.
It couldn't “enter” my portfolio site
Ploy couldn't get past the entry interaction on adityainduri.com, so it never analyzed the data living behind it.
Multiple sites in one workspace was confusing
It wasn't clear whether one workspace is meant to hold many sites — I bumped into friction figuring out the right mental model.
The new-user invite flow drops you outside workspaces
When a brand-new user accepts an invite and clicks their personal organization, they land outside the workspace — because they skipped the setup phase.
Invites say “workspace,” but membership is org-level
Both invite surfaces talk about inviting people to the workspace, yet you can only add or remove members at the organization level. Per-workspace membership control would close the gap.
Small fixes, day-one energy.
None of these are blockers. They're the kind of papercuts and ideas I'd be excited to chip away at as an intern.
Edit existing sites in place
The core job is editing existing or new sites. Copying a live site to edit it introduces errors — especially on dynamic sites. In-place editing would make the whole flow simpler.
A 30-second tutorial at the start
I assumed the sidebar's “sites” meant one space for many sites. Ploy caught the mistake and corrected me — but a short intro would have saved the confusion entirely.
Differentiate workspaces vs. organizations
They feel like the same thing. A little visual and conceptual separation would go a long way.
Selective Google account connect
Let me connect all my Google accounts and then choose which ones each workspace should actually use.
Guard the credit system
Each org gets its own credits. A lifetime-org counter per user would stop people from gaming free credits by spinning up new orgs.
Autofill the email on invite signup
Signup already knows the address it invited — don't ask the new user to type it again.
Handle big dynamic sites
Importing large, dynamic websites hit loading limits. Graceful handling (or a partial import) would help.
Share integrations across an org's workspaces
So I don't reconnect everything per workspace. Even a simple “reuse these connections?” prompt would do it.
Refresh connection status after connecting
Right after I connected an integration, the UI didn't seem to reflect the new connection — a quick refresh of that state would remove the doubt.
From my notes · click to expand
Three real sites, not a sandbox.
The teardown above came from really using Ploy — across three live sites, including this one. Here's what I built with it.
Hephasbot
Browser-native robotics · live on Ploy
Ploy understood my product cold — LeRobot is the powerful open-source stack, Hephasbot is the no-driver browser shortcut to SO-100/SO-101 hardware — and rebuilt my homepage as the “Hugging Face LeRobot, without the terminal” keyword landing page. I added an interactive Command Center preview (connect toggle, six teleop modes, live joint sliders) and the real demo embed, all re-themed to match the brand.
1-click publish · fully responsive
Evidence · click to expand
Pocodex
Open-source Pokémon sprite gallery · 17,190 pets
I cloned the entire production site into Ploy 1:1, then used it to ship serious SEO/AEO: a server-rendered homepage band, a crawlable /pokemon catalog linking thousands of individual pet pages, real Pokédex flavor text per species, an on-brand OG card, and an llms.txt so AI engines can cite it. This is the depth Ploy unlocks once your site is in.
51,570+ sprites · per-pet pages · AEO schema
Evidence · click to expand
ployin around
This very site · the teardown you're reading
Meta proof: the page you're on right now was built entirely on Ploy. Loud Archivo display type, a white→black→lime color-band rhythm, the interactive Ploy-o-matic generator, click-to-expand evidence galleries, and a fused “ployinaround” wordmark — all designed, written, and shipped with the agents, then taken live on its own domain.
Custom domain · interactive · live on Ploy
Evidence · click to expand
I didn't just use Ploy. I stress-tested it.
I'm Aditya — I build robotics products, and I'd love to help build Ploy. I shipped real pages with it, broke it on purpose, and wrote the kind of structured feedback a product team can act on. That's the work I want to do this summer.