Project portability and exit checklist

Included in source export

Downloadable project source and Git sharing include text frontend source, registered backend-module source, blinkhost.yaml, managed module manifests, database schema and migration source, and validated project assets included by the export workflow. Test a representative ZIP before treating it as a recovery copy.

Exports deliberately omit secret values, provider credentials, live database records, browser-local state, build caches, raw platform internals and customer-uploaded backend binaries. Deployment receipts identify verified BlinkHost artifacts, but the compiled backend artifact is not currently offered as a general portable runtime package. Preserve backend source and independent build requirements when portability is essential.

Before disconnecting or terminating

1. Pull or download the final source and verify that it opens outside BlinkHost.
2. Preserve authorized copies of required assets and database schema/migrations.
3. Export live data through a documented workload-specific process; schema files alone are not customer records.
4. Preserve secret names and values in a customer-controlled secret manager. BlinkHost does not reveal stored secret values for export.
5. Record domain DNS, environment bindings, collaborators, billing ownership and retained release identifiers.
6. Test the replacement build, data import and DNS cutover before deleting the BlinkHost project.

GitHub is the currently certified source provider. GitLab, Bitbucket, Azure DevOps and self-hosted Git are not selectable today. Backend modules use BlinkHost's WASI capability model and do not provide unrestricted server processes, filesystems or dependency downloads; keep conventional server workloads separately deployable when they need those capabilities.

Source ownership and Git history

You retain ownership of the code, data and other content you bring to or create in BlinkHost, subject to the limited service licence in the Terms of Service. That rule covers imported frontend source, backend-module source and generated project files; third-party packages and templates remain subject to their own licences.

A connected GitHub repository remains the record for its commits, branches, tags and pull requests. Importing a commit copies its selected project tree into BlinkHost; it does not copy the repository's complete .git database into a project ZIP. Commit and push writes an intentional source commit to the connected branch. A ZIP export contains the current portable project files, not GitHub pull requests, branch history or tags. To preserve complete Git history, clone or mirror the GitHub repository before disconnecting it. An initial export to an empty repository starts that repository's history with the exported project commit.

You may test module source locally against the published SDK and ABI, but BlinkHost does not accept a customer-built binary as a production artifact. Production modules are compiled, validated and signed through BlinkHost's managed toolchain so source identity, plan limits and runtime policy remain enforceable.