Ownership and Portability

Code written in Odyn belongs to you. Odyn stores your source files, builds them, and serves them through a CDN, but it does not claim ownership or impose lock-in on the code itself. This page describes what you own, how to export, and what happens if you leave.

What You Own

• Source files: Every file you create or upload in the editor. These are stored in Supabase and are always accessible via the editor or the export feature.
• Deployment snapshots: Every production deployment includes a full file snapshot of your source files at the time of deploy.
• Version history: The record of all deployments, including metadata, timestamps, and file diffs.

Odyn does not inject proprietary code into your bundles. The built output is standard JavaScript and CSS produced by esbuild. There are no Odyn-specific runtime dependencies in the deployed code.

Export

You can download all project files as a .zip archive at any time:

1. Open the project in the editor.
2. Open the project menu or use the command palette.
3. Select Export. The browser downloads a .zip containing every file in the project.

The exported archive contains your source files with their original paths and content. It does not include built bundles (those are reproducible from the source by running esbuild locally).

Migration

If you stop using Odyn, your code continues to work:

• Source files: Export as .zip and move to any editor or repository.
• Build pipeline: Odyn uses esbuild with standard configuration. You can replicate the build locally with esbuild --bundle --format=iife --target=es2020.
• CDN hosting: Upload the built output to any static hosting provider (Netlify, Vercel, Cloudflare Pages, S3, or your own server).
• Embed codes: Replace the CDN URL in your embed snippets with your new hosting URL.

The transition requires changing the src attribute in your <script> and <link> tags. No code changes are needed.

What Happens to CDN URLs

If your subscription ends or you delete a project:

• Active subscription, project deleted: CDN URLs stop resolving. The R2 assets are deleted as part of project cleanup.
• Subscription downgraded: Existing production deployments remain accessible. You lose the ability to create new production deployments on the Free plan.
• Account closed: All project data and CDN assets are deleted after a grace period.

Pinned URLs (@{version}) do not survive project deletion. If you need to preserve access to a specific version, export the source files or download the built output before deleting.

External Dependencies

External dependencies (GSAP, Swiper, Lenis, etc.) added through the Dependencies panel are loaded from their respective CDNs (jsdelivr, cdnjs, or custom URLs). Odyn does not proxy or re-host these libraries. If you leave Odyn, your external dependency URLs continue to work because they were never served from Odyn's CDN.

No Vendor Lock-In by Design

Odyn's architecture avoids lock-in at each layer:

The only coupling is the CDN URL in your embed snippets. Changing that URL is a single find-and-replace operation in your Webflow custom code settings (or wherever the snippet is installed).