Skip to main content

Open source and third-party notices

Licenses

Assets Studio is built on open source frameworks, internal product code, third-party service providers, and user-provided or AI-generated creative material.

Last updated June 1, 2026

01

Open Source Software

The public landing site uses Next.js, React, Tailwind CSS, Motion, OGL, Lucide, and related Node ecosystem packages under their respective upstream licenses.

The authenticated Assets Studio application uses Laravel, Inertia, React, Vite, Tailwind CSS, shadcn-style interface primitives, PHPUnit, Playwright, and related PHP and JavaScript packages under their respective upstream licenses.

Exact dependency names, versions, and license texts should be reviewed from the shipped package manifests and lockfiles for the deployed version of the product.

02

Product And Brand Assets

Assets Studio product design, interface copy, logos, icons, page layouts, original components, and non-open-source product code are not granted under the open source notices for third-party dependencies.

You may not copy Assets Studio branding, proprietary interface assets, or non-open-source product code except as allowed by a written agreement or applicable law.

03

Generated And Uploaded Content

Generated assets, uploaded references, project prompts, visual identity rules, review comments, and official output selections are not open source merely because they are managed inside Assets Studio.

Rights to use that content depend on the workspace agreement, source-material rights, AI provider terms, and the decisions made by the organization that owns or controls the workspace.

04

Third-Party Services

OpenAI currently powers supported GPT image generation and visual identity drafting features. Future model integrations may include Google Gemini or other providers, each with their own terms, policies, supported capabilities, and data handling rules.

When paid checkout is enabled, Stripe or another payment processor may provide payment, invoice, tax, fraud, dispute, and refund services under the processor's applicable terms and privacy notices.

05

Notice Maintenance

Before a production release or customer distribution, generate and review a dependency license report for the exact build being shipped, then reconcile this page with any notices required by those dependencies and third-party service agreements.