FAQs
Answers to common questions about deployment, licensing, DCC support, and studio rollout.
What is this faqs section for?
Blueprint FAQs answer common questions about the product, studio rollout, trial licenses, DCC support, and pipeline integration.
Blueprint FAQs
Is Blueprint only for large studios?+
No. Blueprint is useful for smaller teams that need repeatable pipeline rules and for larger studios that need scalable workflow control across artists, shows, and vendors.
Can Blueprint work with existing studio tools?+
Yes. Blueprint is designed to connect to existing DCC tools, custom scripts, file conventions, and pipeline services through configurable workflows and APIs.
Does Blueprint require a local license server?+
Blueprint uses a license server workflow so studios can manage users, plugins, activations, and license validation for connected workstations.
Can Blueprint support vendor workflows?+
Yes. Blueprint is designed to package repeatable workflows so external vendors and satellite teams can follow the same production logic.
Can Blueprint be extended by TDs?+
Yes. Blueprint exposes graph workflows, hooks, and Quanta API extension points for custom studio automation.
Is the trial different from a demo copy?+
Yes. The intended model is a trial license, so a user can evaluate controlled licensed access instead of receiving a separate demo copy.