Skip to content
Sign inOpen the bench→

Notes from the workshop

What this build does

Actually runs

  • +Model jobs: text, photo, several photos, and re-texturing a mesh.
  • +The price is quoted before a run; failed and cancelled refund in full.
  • +The shelf, the CC BY 4.0 catalogue, the converter and the viewer.

Not here yet

  • −A real payment processor. The checkout flow is complete and works, but through a simulator: no money moves, and every trace of it says so.
  • −A real email provider. Messages are composed in full and wait in the back office; the operator passes them on.
  • −Referral rewards: the link works and sign-ups are attributed, but no units are paid yet.
  • −Image and video jobs: the tariff exists, the provider does not.
  • −Google/GitHub sign-in, and the REST API.

Right now

Database
…
Generation provider
…
Results arrive by
…

The last column is read straight from this API's own /readyz, not typed in by hand.

Changelog

  1. 0.3[DATE]

    Two to four reference photos

    • +Hand in up to four views and the solver aligns them before building.
    • +The tariff is derived from the provider's prices: one unit is one cent of their cost.
    • +The run reel updates over a live stream instead of polling.
  2. 0.2[DATE]

    The shelf, and files that outlive the provider

    • +Every finished mesh is copied to our own storage the moment it lands, so the provider's expiring link never matters to you.
    • +Failed and cancelled runs refund in one transaction with the status change — the balance and the ledger can never disagree.
    • +Assets can be published to the catalogue, or withdrawn, from the shelf.
  3. 0.1[DATE]

    Bench

    • +One surface: from what, make what. Sentence, photo, several photos or a mesh you already own.
    • +The cost of a run is quoted live and shown on the button before anything is charged.
    • +GLB export, with the triangle budget and quad topology set before the run rather than after.

The dates are left as placeholders on purpose: this build has never been released, so there is no honest date to put there.

Getting help

Support channels and response times
ChannelUse it forReply
The account pageBalance, ledger, changing plan — all self-serveImmediate
Automatic refundsFailed and cancelled runs, refunded in full without askingWithin seconds
Help centre & ticketsAnything the articles do not answer; the ticket is stored and read by the operatorNot promised

No email provider is connected, so a reply to a ticket always appears in the help centre and may never reach your inbox — and no reply time is promised either way. There is no community forum, and no phone number.

The REST API does not exist yet

The plan: submit jobs, poll their state and pull finished files, with exactly the same tariff and the same refund rule as the screens use. There is no endpoint yet, and no waitlist that could store your address.

[WAITLIST FORM OMITTED — nothing would receive the submission, so it would only swallow your address.]