One-click data export — how your assets stay yours
The promise behind Nodipe is simple: the node is your business asset, not a rented storefront. That claim stands or falls on one question — can you actually take your data out? This guide says what “your data” means on a Nodipe node, what an export contains, and how to keep a copy that would survive anything, including us.
What “your digital assets” means on a Nodipe node
Running a node creates five kinds of assets, and they don’t all need the same treatment:
| Asset | What it is | Exported? |
|---|---|---|
| Product catalog | Your product entries — names, descriptions, specifications, pricing, category structure | Yes, in the data export |
| Media files | Product photos, datasheets, certificates, manuals — the originals you uploaded | Yes, in the media package |
| Inquiry & inbox history | Every RFQ and message a buyer sent you through the site | Yes, in the data export |
| Page configuration | Your site’s copy, layout choices, navigation and settings | Yes, in the data export |
| The domain | The address itself, registered to you | Not “exported” — it’s yours independently |
The last row matters more than it looks. Your domain is not a file Nodipe holds; it is an asset registered in your name. The export covers everything inside the node. The domain was never inside it.
What an export actually contains
From your node dashboard you can initiate an export at any time. One action builds a single package you download, containing:
- A structured data file for the catalog, inquiry history and configuration — a machine-readable format such as JSON, with list-style data (like inquiries) also available as CSV if you need to drop it straight into a spreadsheet or a CRM.
- Your media, as the files you uploaded — images and documents at their original resolution, collected into the package rather than compressed or re-encoded.
- A manifest describing what’s in the package and when it was generated, so a copy sitting on a hard drive two years from now still explains itself.
A few honest notes on formats. The exact file layout is a detail we agree with you during onboarding, because the right shape depends on what you’ll feed it into. If your team imports into an ERP or CRM, tell us at onboarding and we’ll aim the export at that system. And because the dashboard and its export tool will keep evolving, if you ever need the current export format documented, ask the founding team — we’ll send you the specification that matches the version you’re running.
Media-heavy catalogs can take a few minutes to package; the export builds in the background and hands you a download link when it’s ready, rather than tying up your browser.
Why a dedicated instance makes this possible
This is the structural difference, and it’s worth being precise about. On a shared multi-tenant system, your data lives in a database shared with other businesses. An export isn’t technically hard — it’s politically hard: the platform decides what “your data” means, and a platform that monetises buyer relationships has a reason to define it narrowly.
A Nodipe node is a single tenant. Your catalog, inquiries and configuration live in a database that is yours alone. There is no other tenant whose data an export would have to tangle with, and no business model that makes a narrow definition of “your data” more profitable. The export is triggered by you, contains everything in the list above, and isn’t gated behind a request or a fee.
Compare that with the marketplace or cart-SaaS path: you can usually export product listings in some form, but buyer contact and inquiry history are frequently the exact data the platform withholds — because holding that data is how the platform keeps you. Export capability isn’t a feature checklist item; it’s a signal of who actually owns the relationship.
Keep a copy that lives outside Nodipe
An export button is insurance, and insurance only pays out if the policy is filed somewhere safe. A healthy habit is simple:
- Run an export after any significant content change — a new product line, a batch of new media, a quarter of inquiries.
- Store the package off-platform: your own cloud storage, an external drive, your IT team’s backup system. Anywhere that is not Nodipe’s infrastructure.
- Keep the data file and its media together — a manifest matters less when the two never get separated.
You do not need to do this often. A handful of exports a year, parked somewhere you control, is enough to guarantee that your catalog, your media and your buyer history are never hostage to a single vendor’s uptime.
If Nodipe ever stopped operating
Straight answer: your domain is registered to you, and your latest export is a complete, portable copy of your catalog, media, inquiries and configuration. Because the data is in open, standard formats rather than locked inside a proprietary product, it can be moved to any hosting that serves standard files — a new site, a different provider, an in-house page.
A founder-run service should not pretend it will run forever. What we can promise is that the thing you’d need to continue — the domain and the data — is never a door only we can open. If you want the reasoning spelled out rather than asserted, the email coexistence guide shows the same principle in a narrower case: the records that make it safe to stay are the records that make it safe to leave.
Troubleshooting
| Problem | What’s happening | What to do |
|---|---|---|
| Export of a large media library seems to hang | Big packages take time to assemble; the process runs in the background | Wait a few minutes, then check for a ready download link rather than re-triggering |
| Download interrupted halfway | Large files can trip flaky connections | Re-download — the package is built once, so a retry doesn’t rebuild it |
| You need the data as CSV, not JSON | Your downstream tool expects rows | Tell us at onboarding which system you import into; list-style data ships in both shapes |
| You’re not sure an old copy is complete | A package copied years ago lacks a manifest context | Run a fresh export — each package is self-describing and timestamped |
Frequently asked questions
Do you charge for exports? No. Initiating an export from your dashboard is part of the service, not a paid feature.
How often should we export? After any substantial content change, and at least a few times a year. Beyond that, exports are cheap insurance you’ll be glad to have if you ever change providers — or if we ever change the world’s plans for us.
Can Nodipe see or edit our exported data? Your node’s database is isolated to your instance. The export is produced from that isolated database; if you need details on how access and isolation work for your deployment, the founding team will walk you through it during onboarding.
What if the export doesn’t cover a specific field we need? The export specification is agreed at onboarding against your real downstream needs. If something is missing, that’s a conversation to have before you rely on it — not after you’ve already left.