Encrypted storage.
Inside your app.

Try our hosted example.

This notebook is operated by Halfpenny Technologies Limited to demonstrate the API. Apps you deploy using the downloadable component are separate services operated by you. How the platform and app fit together →

Opening this page creates nothing. Your first save creates one private pilot store for this browser. Returning visits reuse it.

This is a real pilot store when you press Save. Pilot terms · Privacy. Browser storage is not a backup; save a private recovery file.

One component. Your own app.

<script type="module" src="./vcs-connect.mjs"></script>
<vcs-connect name="my-app"></vcs-connect>

// Inside your app's Save action:
const connection = document.querySelector('vcs-connect');
await connection.save(store =>
  store.set('settings', { theme: 'forest' })
);

Use a unique app name. The component creates a connection on the first save, reuses saved credentials and shows a clear message when setup must wait. It never starts a background retry loop.

If your app offers sharing, the component can create a scoped access link for another device or person. Recovery controls sit under ⓘ. Choose View only or Can edit, with an expiry. Owners can revoke each link under ⓘ. Shared access never permits deleting the store or managing links. Revocation cannot erase downloaded copies. A recovery file can restore the same connection. For customer accounts, use the separate Auth preview or your own authenticated backend.

Does your app need customer accounts?

Use the Auth preview for passkey sign-in and per-customer records. Choose customer-private encryption or app-managed data with authorised support access. Check hosted availability before setup. Use Connect for account-free browser storage, or the Node SDK on a trusted backend.