Source code export

What makes an export useful

Not all exports are equivalent, and the differences decide whether you have portability or a souvenir:

• Standard technologies. Files in HTML, CSS, JavaScript or a mainstream framework can be read and changed by any developer. A proprietary project format cannot.
• It runs somewhere else. The real test is whether the export works when served from an ordinary web host with no connection to the original platform.
• Complete, not partial. Frontend only is common. Ask about the database schema, the data itself, uploaded files, server functions, scheduled jobs and configuration.
• Readable. Minified or machine-generated output that no human would maintain is technically an export and practically not one.

NorthernGo's export is a ZIP of standard HTML, JavaScript and Tailwind on the Premium and Pro plans, which is a deliberately plain target — the generated app is a single HTML document, so there is not much between you and the code.

Why it matters beyond insurance

The obvious argument is lock-in: an export is your exit route if pricing changes, the vendor is acquired or the service shuts down. Three less obvious ones matter more day to day. It lets a developer take over and add the one thing the builder cannot do. It allows an independent security or accessibility review of what actually ships. And it makes version control possible, so you can see what changed between two generations instead of trusting that nothing else moved.

What to watch out for

An export is not automatically a working application. This is the gap people discover too late. Exported files frequently depend on the platform that produced them: an injected database SDK, a hosted authentication service, an AI proxy holding the API key, a build step that only exists in the vendor's pipeline. Every one of those is a call that fails the moment you host the files yourself, and you will not know which ones apply until you try.

So try it early, before you depend on the answer. Download the export from a real project, put it on a plain static host, open the browser console and read the failures. That list is the honest measure of what you own. Repeat it occasionally, since exports drift as platforms add features — and keep the archives, because an export you took in March is worth more than a promise that you can take one in November.