Where our motion data comes from , and where it's going.
This is our public position on the data our models learn from, and on what we owe the people whose movement is in it. It is a versioned document: the version below changes whenever the text does, and every change is recorded at the bottom of the page. Where a statement is not yet backed by something you could check, the page marks it instead of rounding it up.
Last updated: September 1, 2026 · v1.0
Six principles
M—01 / M—06Each principle is marked for what it is. Practice means we do it now. Commitment means we are undertaking to, and it has not been earned yet.
Model index
I—01 / I—03The principles above cover the models Animatica trains. Our product also runs a model somebody else trained, so the index says which is which.
Research prototypes
Trained by
Animatica.
Data sources
Published academic motion-capture sets, AMASS, Human3.6M, Mixamo, Bones, under research and academic terms, several of them non-commercial. Used for prototyping and evaluation, not for the production model.
Our commitments apply?
Yes, we train them, and the terms above are why they stay research work.
Animatica A0, production model, in training
Trained by
Animatica, under the EU co-funded project.
Data sources
Commissioned performances, paid under contract. The dataset is being assembled now, so this describes its scope and not a finished corpus.
Our commitments apply?
Yes, this is the model M—01 is written for.
Trained by
NVIDIA. We built the workflows around them, not the models.
Data sources
Training-data provenance outside our control. We did not select, collect or licence what these models learned from, and we will not describe it as though we had.
Our commitments apply?
No, our commitments apply to the models we train ourselves.
Generating with either still does not put your motion into a training set; M—03 is about our servers, not about who trained the model.
What we are still cleaning up
C—01 / C—04A register of open items. Each one closes by being published here.
What we are not building
RenunciationsNo text-to-finished-film.
We are not building a machine that turns a sentence into a finished shot. We build the frames between your poses, under your direction. The shot stays the animator's to make.
No training on your scenes.
What you send to the hosted backbone comes back to you and goes no further. Self-hosting keeps it off our servers entirely. This one is policy, not aspiration.
No cloning a living artist's style without consent.
A style belongs in the Motion Library because the person who performed it put it there on terms they agreed to. We will not reconstruct someone's motion signature from their published work and sell it.
What this means in practice
Check it yourselfYour keyframes are a constraint.
The model fills the frames between the poses you set. It does not move the poses.
See it in Blender →The result is editable frames on your rig.
Not a video and not a locked take. Generated motion arrives as keys you can select, retime and delete like your own.
See it in Motion Builder →You can run it without us.
The generation backbone is open source under Apache-2.0. Self-host it and your scenes never reach our servers.
Hosted or self-hosted →Motion Library
Collecting interestM—06 needs a mechanism, and this is the one we are building. Performers and studios contribute style packs, their own motion, on terms they agree to. Those styles condition generation for people who pay to use them, and the contributor earns from that use rather than from a one-time sale. Because a style conditions generation instead of being baked into weights, a contributor who withdraws one actually removes it.
None of that exists yet. There is no marketplace, no payout, and no date we are prepared to publish, announcing one we then miss would cost exactly the credibility this page is built on. What exists is this list, and the intention to open a pilot from it.
What would prove us wrong
AccountabilityA page like this is worth something only if it can be shown to be false. Three findings would do it.
Motion in one of our training sets that came from scraping, or from a source we did not licence.
A model of ours trained on the scenes customers sent to the hosted backbone.
A contributor asking us to withdraw a style, and us being unable to remove it.
If you find one, write to hello@animatica.ai. We undertake to answer a question about where our data came from publicly, within 48 hours. A correction gets a line in the changelog below rather than a silent edit.
Changelog
v1.0 , initial publication (September 2026).