Polotno SDK ships as a minified, production-ready JavaScript bundle with deep customization options exposed through its public API. For nearly every integration — from SaaS design tools to enterprise creative systems — this provides complete flexibility without touching the internal source code. The SDK supports extensive UI modifications, custom logic, and rendering pipelines through configuration and extensions alone.
Still, some enterprise clients require direct access to the core codebase for legal, compliance, or contingency reasons. Source code access exists for those cases, but it’s gated, licensed separately, and governed by specific enterprise conditions.
Default distribution
By default, Polotno SDK is provided as a minified build. The editor, rendering engine, and schema are all accessible through documented APIs — no uncompiled source is included. Developers can modify panels, add new element types, integrate external rendering, and automate project creation programmatically without direct core access.
In practice, 99% of Polotno implementations — including advanced, large-scale deployments — never need the raw source code.
ㅤ
Source code availability
Full source access is exclusive to Enterprise clients ($599+/mo) and provided through a separate one-time licensing agreement. The agreement includes a non-compete clause and governs usage, updates, and confidentiality.
The typical starting price for source code access is $50,000, quoted individually depending on project scope, company size, and intended usage. Access is granted via a private GitHub repository.
As long as a company maintains its Enterprise subscription, it retains access to the repository and receives all product updates. If the Enterprise subscription is terminated, access to both the repository and future updates is revoked.
Source code access does not transfer ownership or redistribution rights. It’s strictly for internal development, review, and audit purposes under a non-transferable license. Clients may modify the code for their own use but cannot resell or redistribute the SDK.
ㅤ
Why companies request source access
Most source code requests come from legal or procurement departments, not engineering. Enterprises often require source availability as a safeguard — to mitigate vendor risk or ensure continuity if product availability changes.
A smaller fraction of clients use it for deep core customization, such as extending rendering behavior or implementing domain-specific design constraints. These cases are rare and generally handled by teams with significant internal engineering capacity.
ㅤ
Summary
Polotno SDK provides complete flexibility through its public API and schema system, making source code access unnecessary for nearly all customers. The optional Enterprise-level source license exists primarily for compliance and long-term assurance. It’s a separate, one-time purchase bound by non-compete terms and maintained only while the client remains on an active Enterprise plan.