One private vault per account

Never solve the same
error twice.

DevVault is the searchable memory for everything you debug, copy and look up again: errors and the fixes that actually worked, snippets, commands, playbooks and project logins — one vault, one search box.

Create your vault See what it holds

Already have an account? Sign in.

DevVault — errors

SQLSTATE[42S02]

2 matches — searched as you typed

SQLSTATE[42S02]: Base table or view not found: 1146

laravel checkout-api seen 7× resolved

Worked: migrations ran against the wrong connection — set DB_DATABASE in the queue worker's env and restart it.

SQLSTATE[42S02]: table "jobs" missing after deploy

mysql billing resolved

11 sections

Errors, snippets, commands, credentials and more

Live search

Full-text results across the vault as you type

Team-ready

Keep a personal vault, share a workspace

Export anytime

The whole vault as a zip, no lock-in

The error log

A bug you have already beaten should cost you seconds.

Every entry keeps the message, the stack trace, the project it came from — and every fix that was tried, marked by whether it actually worked.

Solutions, not guesses

Log each attempt against the error and mark the one that worked — it resolves the error automatically. Screenshots, log excerpts and config files pin to the entry alongside it.

Answers as you type

MySQL full-text search runs live across the vault, and shared tags pull related errors and snippets together. No waiting on a button, no folder to remember.

Repeat offenders surface

Paste an error into Quick Log and DevVault checks the vault as you paste, warning you if it is already solved. Recurrences bump an occurrence counter that ranks the worst offenders on the dashboard.

The rest of the vault

Everything else you keep re-finding.

The same treatment for the other things that live in scratch files, chat history and browser tabs.

Snippets

Syntax-highlighted, one-click copy, ordered by how often you actually reach for them.

Commands

The terminal one-liners you always look up again — copyable, tagged, per project.

Credentials

Project logins grouped by project, passwords encrypted at rest, with bulk paste straight from a spreadsheet.

Playbooks

Ordered setup procedures with copyable steps — import one, export one, hand it to the next person.

Links

The pages you keep going back to: pinned, foldered, and ranked by how often you open them.

Tasks

What is in progress and what got finished, with a printable PDF report for the week.

Sites

Watch the addresses that matter and hear about it the moment one stops answering — checked as often as every minute, confirmed twice before anyone is told, and told again when it comes back.

Alerts

Point a channel at your vault and hear about an error the moment it arrives — Slack, Microsoft Teams, Google Chat, or plain email. The same goes for a site that stops answering.

Digest and project stats

Which project is noisiest, what went quiet, what got fixed lately — exportable as Markdown.

Workspaces

Invite teammates by email, set roles, and move or duplicate items between a personal and a team vault.

Export and import

One zip holding a re-importable vault.json, a readable Markdown archive, and your attachments.

How it works

Capture, solve, reuse.

The loop is short on purpose — anything slower than the problem itself stops getting used.

Capture it where it breaks

Paste the error into the Quick Log modal from any page, or let your app POST it to the API the moment it throws. Either way the vault warns you if the fault is already on file.

Record what actually worked

Add the things you tried as you try them. Mark the winner and the error resolves itself — including the dead ends, which are worth as much as the fix next time. Or let the fix checker read your own commit history and tell you which of your open errors you have already fixed without noticing.

Find it again in seconds

Search runs as you type across the whole vault. The dashboard keeps repeat offenders and recent activity in view, so patterns show up before they cost you another afternoon.

Auto-capture

Let your apps file their own errors.

Mint a write-only token in settings and point any application at the capture endpoint. A crash loop becomes one entry with a big occurrence count — not five hundred identical rows.

Tokens can log errors and nothing else
A token can target a specific workspace
Identical faults merge by fingerprint, not guesswork
An error arriving can be announced in Slack, Microsoft Teams, Google Chat or by email.
Fixed and quiet for ninety days? It leaves the list on its own, and stays findable.

POST /api/errors curl

curl -X POST https://devvault.fsulit.net/api/errors \
  -H "Authorization: Bearer $DEVVAULT_TOKEN" \
  -H "Accept: application/json" \
  -d error_message="SQLSTATE[42S02]: Base table not found" \
  -d project_name="checkout-api" \
  -d environment="production"

{"status": "occurrence", "occurrences": 7}

Your data

Private by default, and yours to take with you.

A vault is only useful if you trust it with the things you would not paste into a chat window.

Nothing is shared by accident

Everything you log lands in your own vault. Other people see it only when you invite them into a workspace and put it there.

Credentials encrypted at rest

Stored passwords are encrypted in the database, not sitting in plain text next to everything else.

Account recovery that holds up

Recovery codes, a verified backup address, and a list of signed-in devices you can sign out remotely.

No lock-in

Export the whole vault whenever you want — a re-importable file and a readable Markdown copy, in the same zip. It also runs nightly on its own, encrypted, because an escape hatch somebody has to remember to use is not one.

Start with the error you fixed yesterday.

One entry is all it takes to be ahead the next time it happens. Create an account and paste it in.

Create your vault Sign in

Your account	Name, email address, an optional recovery email, your password as a one-way hash (it cannot be read back), recovery codes as hashes, and when you agreed to these terms and this notice.
What you save	Errors, solutions, snippets, commands, playbooks, links, tasks, tags and attached files, in the workspace you save them in. Each solution records who wrote it.
Credentials	Usernames and URLs as you enter them; passwords encrypted in the database. Only workspace members with credential access can open them.
Errors your apps send	The error message, stack trace, project name, environment, language and framework (see what the handlers send).
API tokens	A name, what the token may do, the workspace it belongs to, and when it was last used. The token itself is stored only as a hash: DevVault shows it once, when you create it, and never again.
Signed-in devices	Each session's browser and IP address, so you can see where you are signed in and sign other devices out (Settings → Account).
In your own browser	A session cookie to keep you signed in, and a few display preferences (light or dark, collapsed sections, playbook progress) kept in your browser only and never sent to DevVault.

Token	Can	Cannot
App token (Log errors)	Send errors into one workspace.	Read anything stored in DevVault: not your errors, not your credentials, nothing. All it ever gets back is the number of the error it just sent, and, from the connection check, its own name and its workspace's name. A leaked one gives nothing else away.
Fixes token (Read errors, Add solutions)	Read the errors of one workspace, and add solutions to them.	See any other workspace, your credentials, snippets or anything else; edit or delete anything.

Never solve the same error twice.