OpenVibe.Space · spaces

Make a space. An app on your OpenVibe account.

Describe what you want and OpenVibe AI builds it, or start from a template and change anything in the editor. A space signs visitors in with OpenVibe, keeps shared lists and private data, and talks to OpenVibe AI.

Make a spaceBrowse spaces

The builder, the editor and the preview work for everyone signed in. Publishing a space at its own address opens with public hosting.

Start from a template

Each one is a working space you can open in the editor and change: sign-in, data and AI already wired.

GuestbookVisitors sign in and leave a note for everyone to read.AI buddyA chat with an AI character you describe; each visitor's conversation is kept for them.Quick pollOne question, a few answers, one vote each, live results.Reaction gameClick when it turns green; best times go on a leaderboard.TriviaQuestions whose answers stay on the server (a space function), with how many got each right.Private to-dosA to-do list saved to each visitor's own account.

How a space comes together

  1. Describe it, or pick a templateSay what the app should do and OpenVibe AI writes a first version, or open a template.
  2. Change anythingThe editor shows your space's files with a sandboxed preview beside them, so every change is visible at once.
  3. Sign-in, data and AI built inThe space SDK gives you the visitor's OpenVibe profile, shared lists, private storage, OpenVibe AI and server functions.
  4. Share itPeople open it with their OpenVibe account; publishing at its own address opens with public hosting.

Static hosting: publish a site, keep every deploy.

Immutable, content-addressed deploys with one-step rollback, previews, Git deploys and verified custom domains. OpenVibe staff host here today; it opens to everyone once abuse handling and a designated DMCA agent are in place.

Hosting dashboardHow it works

How a deploy works

  1. Make a project and a siteA project holds sites and the people who may change them. Each site gets its own address under openvibe.website.
  2. Upload, or connect GitUpload a folder or a .tar.gz from the dashboard or the API, or deploy from a public Git repository. Nothing is built or executed: the files are served as they are.
  3. Preview, then activateCheck a deploy at its private preview address, then make it live. Activation switches one pointer, so rolling back is one step too.

What works now

Immutable deploysEvery deploy is content-addressed and kept: files are stored once by their hash, and a deploy never changes after upload.
Previews and rollbackA private preview for the project's members, one-step activation, and a rollback to the deploy that was live before.
Git deploysPoint a site at a public repository and branch; each ingest lands as a preview for someone to approve.
Your own addressSites serve under openvibe.website. A custom domain is served once its TXT record proves it is yours.
Headers and redirectsPer-site response headers, redirects and a single-page-app fallback. Platform security headers always win.
Members and rolesOwners, maintainers and deployers per project; an app can deploy too, with a grant and a role, never as the owner.
Takedowns kept for reviewOpenVibe staff can stop serving a site or a whole project while its content is kept for review, and lift it again.
An API for all of itProjects, sites, deploys, domains and configuration over /api/v1, with OpenVibe.Network tokens and space.* capabilities.

The same over the API

With a Network token for openvibe.space that holds space.deploy.create and a role in the site's project.

Upload and activate a build
tar -czf site.tar.gz -C dist .
curl -X POST "https://openvibe.space/api/v1/sites/$SITE_ID/deploys?activate=1" \
  -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/gzip' \
  --data-binary @site.tar.gz

Quotas per project

What a project may use today; staff can raise a project's quota.

LimitProductionSandbox
Storage1 GB100 MB
Deploys per day5020
Sites103
Custom domains50
Files per deploy10,0002,000
Largest file25 MB10 MB

These are the limits the service enforces, read from github.com/OpenVibers/OpenVibe.Space/blob/main/server/hosting-config.js.

Questions

What is a space?

A small app on your OpenVibe account: a page with your own code that signs visitors in with OpenVibe, keeps shared lists and each visitor's private data, can call OpenVibe AI, and can run server functions.

Do I need to know how to code?

No. Describe what you want and OpenVibe AI builds a first version, or start from a template. Everything is editable in the editor, with a live preview beside it.

Who can use a space I make?

Anyone you share it with signs in with their OpenVibe account. Each visitor's private data is theirs; shared lists are what everyone in the space sees.

Can I publish a space at its own address?

Publishing at its own address opens with public hosting, once abuse handling and a designated DMCA agent are in place. The builder, the editor and the preview work for everyone signed in today.

What is static hosting?

Immutable deploys of a built site with previews, one-step rollback, Git deploys and verified custom domains under openvibe.website. OpenVibe staff host on it today; it opens to everyone with public hosting.

Where did the forum go?

The forum moved to OpenVibe.Community; old links redirect there.

Looking for the forum?

The forum moved to OpenVibe.Community.

Open the forum