Your next idea.
A little persistence.
Storage infrastructure for developers: persistent data for your app, with optional passkey accounts. Start with app-managed Auth for ordinary apps, or choose client-held encryption when you need it.
Account-free stores are available now. Customer accounts use the separate Auth preview.
Build with us.
We’re looking for the first five builders to try VibeCodeStorage in a small project. Use sample data, tell us what gets in the way, and help shape the pilot.
Try Project Desk and copy the coding-agent prompt → · Join the pilot
Building with a coding agent?
Start with our integration instructions and ready-made Node.js setup module. For static browser apps without customer accounts, use the ready-made Connect component for a private store per visitor. For shared data, the Node.js module saves and reuses one private store on your backend, including after interrupted setup. Use /health to check connectivity; do not create test stores.
When new-store creation is busy, the API returns a retry time. Keep the saved setup files and stop until then; existing stores remain usable.
A few commands. A saved idea.
Install Node.js 24 or newer, then run:
npm install --global vibecodestorage
vibecodestorage init --endpoint https://api.vibecodestorage.com
vibecodestorage set settings '{"theme":"dark"}'
vibecodestorage get settingsRead the Terms of Service and Privacy Notice before creating a store. Make your first successful write within four hours to activate a new store. Keep your local credentials and recovery file private.
Account-free stores keep encryption in your client.
The SDK, CLI and encryption code are publicly available under the MIT licence, with client tests you can run yourself.
Encrypted before upload
The official SDK encrypts labels and values with AES-256-GCM. Your encryption key stays with your client.
Your credentials, your store
A store ID, access token and encryption key provide access. There is no email account or password-reset flow.
Export when you need to
Export through the CLI or SDK. Exports contain plaintext, so store them securely and keep your own backups.
Built for experiments, for now.
This is a limited pilot with capacity for 200 active stores. Availability, long-term retention and recovery are not guaranteed. Do not use it for sensitive personal data, regulated workloads or your only copy of important information.
Billing is disabled. Any future paid service will require separate agreement. Browser apps can use a private store per visitor over HTTPS or localhost. Shared owner credentials require a trusted backend; never publish them. Auth preview uses customer sessions instead.
Your app, our storage API.
You build and operate the app, choose its audience and manage user access. We operate the encrypted storage service. Client components run in your app and are optional; Connect is account-free; the separate Auth preview provides passkey accounts.
One clear API address.
https://api.vibecodestorage.comDoes 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.