$49 / month
For a single creator working with their own passports.
- Frame, Motion and Restyle Two Creator Passports Signed manifests on every export 1080p delivery
Creator, roster and enterprise access for teams that need media generation, Creator Passport identity, rights-aware authorization and provenance to operate as one system.
Access
The plans below preserve the current Neuto commercial model while separating creator experimentation, roster operations and infrastructure-scale deployment.
$49 / month
For a single creator working with their own passports.
$390 / month
For a roster. Rights teams get their own view of the record.
Custom
For platforms embedding the studio behind their own front door.
What access includes
Neuto is designed as media infrastructure. Commercial access combines creative tooling with the identity, rights and evidence controls needed to move generated media into real operating environments.
Directable motion, frame, voice, likeness and transformation workflows with production-oriented controls.
Persistent identity and asset context connecting creators, organizations, voice, likeness and media records.
Rules and decision records that help teams evaluate whether a requested AI action fits the represented permissions.
Source-to-output relationships, model references, signed manifests and operational audit records for reviewable workflows.
Enterprise deployment
Enterprise engagements can be structured around integration scope, deployment model, workspace architecture, security requirements, support and the volume of authorization or provenance activity.
Workspace design, role boundaries and deployment options aligned to enterprise governance and operating requirements.
Embed verification, rights authorization and provenance workflows behind your own product or operational interface.
Role-based access, workspace isolation, scoped credentials, auditability and deployment-specific security review.
Custom terms can reflect implementation, service requirements, expected volume, support coverage and integration complexity.
Plan comparison
| Capability | Studio | Label | Enterprise |
|---|---|---|---|
| Primary operating model | Individual creator | Roster + rights team | Platform or organization |
| Creator Passport scope | Up to two passports | Unlimited roster passports | Workspace and integration scope |
| Media workflows | Frame, Motion, Restyle | Expanded voice + likeness workflows | Configurable to deployment |
| Provenance | Signed export manifests | Roster-level records | API, webhook and audit export |
| Developer integration | — | API access | API + webhooks + custom integration |
| Deployment model | Neuto hosted | Neuto hosted | Hosted, private or scoped deployment |
| Commercial structure | Monthly | Monthly | Custom agreement |
Implementation
For enterprise and roster environments, pricing is only one part of the deployment. The engagement is structured around how Neuto will fit the actual rights and media workflow.
Define creators, assets, rights signals, approval steps, media outputs, integration boundaries and success criteria.
Set workspace access, Creator Passport records, policy requirements, authorization rules and provenance expectations.
Connect the required API or product surfaces, test representative workflows and establish an operational review process.
Commercial FAQ
The current plans package the media workflow with Creator Passport and provenance capabilities. Larger deployments can be structured around the specific mix of generation, authorization, API and audit usage.
Yes. A pilot can start with a defined creator or catalog cohort before expanding to a broader rights operation.
Yes. Infrastructure-level deployments typically require agreement on scope, security, service expectations, permitted usage and commercial terms.
Enterprise access is designed to support API and webhook integrations so Neuto capabilities can sit behind an existing user experience or operational workflow.
No. Neuto provides technical identity, policy, authorization and provenance infrastructure. It does not replace contracts, rights-holder authority or applicable law.
Request a demo and provide your organization type, expected workflow, creator or asset scope and integration requirements. The commercial structure can then be scoped around the deployment.
Next step
Tell us what you are building, the rights context involved and where Creator Passport needs to connect.