Project export
A project's data is yours to take elsewhere. On the project's page in the portal there are two downloads. Neither contains a secret: credentials appear by id and last four characters only, and no token is ever written into either.
Metadata (JSON)
Any member can download it. It is one JSON document (openvibe.codes.project-export v1) with what OpenVibe.Network holds for the project (the project, members, apps, credentials, grants and quotas, plus the audit log for admins) and what Codes holds (releases with their manifests and logs, trust tiers, playground runs). If Network fails part-way, you get an error, never half a document.
Full archive (zip)
The owner and admins can download it. Codes asks OpenVibe.Network for a read-only export token for each service and environment. Network checks your role, records the request in the project's audit log, and the token lasts five minutes. Codes then reads the project's data with it. Codes keeps nothing of the archive.
| File | What it holds |
|---|---|
manifest.json | format (openvibe.codes.project-archive v1), counts per part, whether each part is complete and where it stopped, every file with its size and SHA-256, and what is not included |
README.txt | the same in words, with a one-line script that fetches the objects |
project.json | the metadata document above, with the audit log. This is the project's configuration: environments, allowance, apps and redirect URIs, grants, quotas |
modules/<release_id>.json | each release's manifest (codes.app-manifest@1 or mods.mod-manifest@1) exactly as validated |
media/<env>/namespaces.json | OpenVibe.Media's namespaces for the project: policy, quotas, usage |
media/<env>/objects.jsonl | every object, soft-deleted ones included, one per line with Media's metadata and download: a public URL, or a signed one valid for 60 minutes |
events/<env>.jsonl | the project's app events (app.<project_key>.*) that OpenVibe.Events still keeps, one { seq, event } per line |
<env> is production and sandbox, both always present (empty when the project has nothing there).
- Objects are listed, not copied. A project can hold gigabytes; the zip holds each object's URL, and the bytes come straight from Media. Fetch them before the signed URLs expire, or download the archive again for fresh ones.
- Limits. At most 5000 objects and 10000 events per environment. A part that reaches its limit says
complete: falseand the cursor to continue from, and so does the archive as a whole. - All or nothing. If Network, Media or Events fails or refuses, the page names the service, part and environment, and nothing is downloaded.
- Retention. Events keeps app events for a limited time (see Limits); older ones are gone before any export.
- Not included: Tools job results (readable only by Tools), Events webhook subscriptions (each app's own, with signing secrets), and Network user modules (per person, not per project: each member exports their own from Network).