Riggle vs Polywink: a VRM you can stream, at a VTuber price
Polywink automates blendshape generation for studios. But it never emits a VRM, and it's priced and paced for film and games — not for a VTuber finishing one model.
Polywink fully automates ARKit blendshape generation with a ~24h turnaround, but it outputs FBX/Maya/Unity/Unreal formats — never VRM — and is priced for studios. Riggle is the VTuber-shaped alternative: it generates the same 52 ARKit shapes, wires them into VRM 0.x/1.0 clips, validates the model, and returns a download in minutes for about a dollar a model. If you're a studio shipping to a game engine, Polywink fits. If you want a perfect-sync VRM for VSeeFace or Warudo, Riggle is built for that.
Polywink: studio-grade, but not VRM
Polywink (Blendshapes on Demand / Animation on Demand) is a genuinely automatic service — send a neutral face, get back the ARKit shapes, typically within 24 hours. It's aimed at film, games and enterprise, and it's good at that.
For VTubing it has two mismatches. First, format: it delivers FBX, Maya, Unity or Unreal assets, never a VRM — so you're back to rebuilding the VRM yourself. Second, pricing and pace: studio quotes and a day's turnaround don't fit someone finishing a single $30 avatar.
Riggle: VRM-native, minutes, a dollar a model
Riggle is the same idea — automatic shape generation — repackaged for VTubers:
- VRM in, VRM out. It wires the shapes into VRM expression clips and returns a validated .vrm, not an engine asset you have to convert.
- Minutes, not a day. Upload and download in the same browser session, with an in-browser preview of every shape.
- VTuber pricing. Model packs — $9.99 for 10 models or $29.99 for 50 — with free re-rigs after edits, the bigger pack aimed at sellers doing volume.
- Right defaults. The 52 ARKit shapes plus the VRM expressions and A/I/U/E/O visemes the VTuber apps expect.
Side by side
| Polywink | Riggle | |
|---|---|---|
| Auto-generates 52 shapes | Yes | Yes |
| Outputs a VRM | No — FBX/Maya/Unity/UE | Yes (0.x & 1.0) |
| Turnaround | ~24h | Minutes |
| Audience & price | Studio quote | $9.99 / 10 models |
| In-browser preview | No | Yes |
Which should you use?
If you're a studio piping faces into Unity or Unreal and you want enterprise turnaround and support, Polywink is built for that. If you're a VTuber or base seller who needs a perfect-sync VRM for VSeeFace, Warudo or VMagicMirror — fast and at a self-serve price — Riggle is the one that actually hands you the model you'll stream with.
A VRM you can actually stream with
Riggle generates the 52 ARKit shapes and returns a validated VRM in minutes — VTuber-priced, no engine conversion.
Enter your email to get started
Any topology · VRM 0.x & 1.0 · check readiness free · re-rigs are free.
FAQ
Does Polywink output VRM files?
No. Polywink delivers FBX/Maya/Unity/Unreal formats, so you still have to convert to VRM yourself. Riggle outputs a validated VRM directly.
Is Riggle faster than Polywink?
Yes — Riggle returns a model in minutes in the browser, versus Polywink's roughly 24-hour turnaround.
Is Riggle cheaper for a single avatar?
For a VTuber finishing one model, yes — model packs from $9.99 for 10, about a dollar a model, with free re-rigs, versus studio-oriented quoting. Polywink is designed for production pipelines, not one-off avatars.