API keys and tokens

Your API keys do not belong in a text file.

Rempar is a zero-knowledge vault where developers keep their API tokens, SSH keys and certificates, encrypted on the device with one key per item. It replaces the notes files, the messages sent to yourself and the screenshots where these secrets too often end up.

Where developer secrets end up

An API token is a password in disguise: whoever holds it acts on your behalf with the service, often with no two-factor authentication. Yet it is frequently shown only once, when it is created, and it has to be put somewhere.

  • A notes file or a .env file copied from project to project.
  • A message sent to yourself or to a colleague in a chat app.
  • A configuration file pushed to a code repository by mistake.

What goes into Keys and tokens

The Keys and tokens category in Rempar holds the technical secrets that are neither website accounts nor servers. Each item has its own 32-byte key, sealed by the vault key: opening one token decrypts only that token.

  • API tokens: hosting providers, payment services, continuous integration platforms.
  • SSH keys: deploy keys and personal keys.
  • Certificates and their private keys.
  • Secure notes: environment variables, backup codes, sensitive procedures.

Copy a secret without leaving it lying around

In Rempar, a secret is hidden by default and only shown on an explicit gesture, then hidden again after 30 seconds. The clipboard is cleared 30 seconds after a copy, which keeps you from pasting a token into a conversation by accident an hour later. Rempar 1.2 remains a vault: you copy the value to where it needs to go, for example into the secrets settings of your deployment platform.

Good habits for your tokens

A vault does not replace good token hygiene; it makes it practical.

  • Create one token per use and per machine, with the narrowest permissions possible.
  • Note in the item what the token is for and where it is deployed, so you can revoke it without hesitation.
  • If a token has been pasted into a message or a repository, treat it as compromised and replace it.

Local, Cloud, and soon Claude

Local mode is free, with no account and no item limit: your tokens stay in an encrypted file on your machine. Cloud mode syncs the vault end to end across macOS, Windows, Linux, Android, iPhone and iPad for €2.99 per month or €29 per year, after a 7-day free trial. Rempar 1.3 will bring a Claude connector (MCP), which will let you entrust the use of a token to Claude without handing over its value by default. This feature is not available in version 1.2.

FAQ

Can I keep the contents of a .env file?

Yes, by pasting it into a secure note. The note is encrypted on the device like any other item, with its own 32-byte key. You keep a reference copy of your secret variables without leaving the file in plain text in a chat app or a shared folder.

Does Rempar replace an infrastructure secrets manager?

No. Rempar is a personal vault: it holds the reference copy that you, a person, need in order to create, find or rotate a token. Secrets read by your applications in production belong in a tool built for that purpose within your infrastructure. The two complement each other.

Can the Rempar server see my API tokens?

No. In Local mode, nothing is sent to a server. In Cloud mode, every item is encrypted on your device before it is uploaded, with a key the server does not hold. It sees neither the value of the token, nor the name of the item, nor your master password.

Updated on November 12, 2026

Start locally, for free.

The local vault is complete, free and needs no account. Cloud adds end-to-end encrypted sync across your devices, with a 7-day free trial.