Creative flexibility.Deliberate boundaries.
An overview of the controls built into JsonCut. Contact us for the security information and processing agreement applicable to your organization.
What is built in.In plain words.
How workspaces, project versions, media, custom code and rendering are kept apart and recoverable.
- Tenant isolation
- Projects, templates, media and operations are authorized against the owning workspace rather than accepted from a client-provided identifier alone.
- Validated project writes
- V2 project versions are validated before persistence so an invalid document cannot silently become the next editor state.
- Scoped media access
- Uploads and downloads use scoped references and temporary access where appropriate; project media is not treated as a global public pool.
- Isolated custom code
- Custom HTML, CSS and JavaScript run in a restricted project-timed environment with network, storage, navigation and parent access blocked.
- Minimal public surface
- The developer API and MCP server expose production workflows, while internal Studio and recovery operations remain private.
- Operational recovery
- Queues, renderer leases, idempotent jobs and storage checks are designed to recover work without duplicating successful outputs.
Have a security question?Ask the people who build it.
Contact the JsonCut team for architecture, processing and data-handling questions relevant to your workflow.