Skip to main content

Roadmap

What's built, what's missing, and what isn't promised.

Sculptly is one person's project in private beta. That rules out a board with dates on it — anything scheduled here would be a guess dressed up as a commitment. So this page lists three things instead: what already works, what is known to be missing, and what has been decided against for now.

Already in

Each of these is live and reachable today, not staged behind a flag:

  • Image-to-3D generation — upload a photo, sketch, or concept image and get a GLB mesh back, billed against a credit ledger with Stripe checkout for packs and subscriptions.
  • Eleven free browser tools — voxelizer, mesh repair, OBJ to STL conversion, STL to 3MF conversion, an STL simplifier, mold generator, scene composer, splat viewer, a GLB viewer, print cost calculator, and lithophane generator. All run locally in the browser; no account, no credits, no AI call.
  • A safety check before the charge — unsafe images are refused before any credit is spent, rather than after.
  • Share pages and embeds — a generated model can be given a public page and an iframe embed.
  • Daily check-in credits — shipped, then retired on 11 September 2026. Of the 35 accounts that ever claimed one, 32 claimed exactly one and never came back for a second, so it was not buying the return visit it existed for. Accounts that already have grants keep them; new accounts get the signup credits and then the plans.

Known gaps

These are real holes, listed because finding out from a support ticket is worse than reading it here first:

  • Text-to-3D is two steps, not native. A sentence becomes one reference image and the normal image-to-3D run builds the mesh from it. If you want a model generated straight from text, the comparison page names the competitors that do it.
  • No retopology pass. What you download is the raw mesh from the model, cleaned only as far as the free mesh-repair tool will take it. There is no automatic quad remesh.
  • Rigging is humanoid-only. Upright humanoid characters can be rigged with a walk and a run. Animals, props and everything else come out static, and there is no animation library.
  • Several photos only on High Detail. Back, left and right reference photos improve the hidden side, but only on the High Detail tier.
  • The domain isn't bound. The site is served from a workers.dev address. A domain has been bought but not yet pointed at the app, and the support address printed in the site's own configuration still belongs to a domain that resolves nowhere — which is why the contact form is the reliable route.

Not doing, for now

  • Referral and invite mechanics. Cheap to bolt on, and it would inflate signup numbers without improving the thing people actually came for.
  • A marketplace or asset store. Sculptly's job ends when you have the file.
  • Enterprise plans, SSO, seats. There is one person here. Selling a support commitment that can't be honoured is worse than not offering it.

How this list changes

Requests move things up it. If something you need is in the gaps section, saying so through the contact form is the most direct way to affect what gets built next. Shipped work gets written down on the changelog — that page is the record, this one is the intent.