# Your cards, synced on your own server.

> Run QuanCard's sync service and web vault on your own server. iPhone and browser stay in sync, end-to-end encrypted; the server stores only ciphertext. Open-source server, one-command deployment.

Source: https://quancard.app/en/server/

Run the sync service and the web vault on a server you control. iPhone and browser stay in sync, encrypted, while the server stores only data it cannot read. The server is open source and auditable, and it is yours to run.

## Let an AI assistant install it

Copy a prompt for Claude Code, Codex and others to install safely with the official Skill.

Copy this prompt into an AI assistant that can run commands on your server, such as Claude Code, Codex or Cursor. It checks your environment, asks before changing anything, and follows the official Skill to install and verify.

```
Please install QuanCard Server (the self-hosted sync service and web vault for the QuanCard iPhone app) on my server.

First read and strictly follow the official install Skill:
https://quancard.app/.well-known/agent-skills/quancard-server-install/SKILL.md
If you cannot read it, use https://quancard.app/en/server/docs/ and https://github.com/zoolapp/quancard-server instead.

Requirements:
1. Start with read-only checks only (OS, Docker, DNS for my domain, whether ports 80/443 are in use, any existing reverse proxy). Report what you find, recommend an install path, and wait for my confirmation before changing anything.
2. Install the latest published release and pin its version. Read any downloaded script before running it and tell me what it does.
3. Never write .env, QC_SECRET or the setup token to logs or commits, or send them to any external service. Never ask me for card numbers, passwords or other vault data.
4. Ask before deleting data, overwriting existing configuration, changing the firewall or restarting existing services. Keep the official container hardening.
5. When done, verify each item (valid HTTPS certificate, /healthz, port 8080 not exposed, .env mode 600, backup script works), give me a short report, and tell me how to create the owner account and pair my iPhone.

My domain: vault.example.com (replace with yours)
```

The prompt only describes the installation. It never needs card details or passwords, so do not add any. [View the Agent Skill](https://quancard.app/.well-known/agent-skills/quancard-server-install/SKILL.md)

## Sync across devices

iPhone and the web share one revision protocol, so a change on either side appears on the other.

## Fully self-hosted

One Docker Compose file with automatic HTTPS. You choose the domain, the backups and when to upgrade.

## Secure and in your control

Cards are encrypted on your device before they sync. The server never sees a card number or your password.

## Scan once. Both sides are ready.

Create a one-time QR code in the browser and scan it with your iPhone. The key goes from the browser to the phone and never passes through the server.

- One-time pairing code: The code expires after 10 minutes and works once. You confirm your password before it appears.

- Confirmed on both sides: The moment the phone connects, the browser confirms it. Both screens play the same linked animation and show the first sync.

- Always current: The web refreshes when you return to the tab, and every 60 seconds while it is open. The iPhone syncs on its own schedule.

## Your data on your server. Readable only by you.

Your cards are encrypted before they leave your device. Even if someone gets hold of the server or a backup, all they find is data they cannot read.

- 01: Encrypted on your device: Cards are encrypted on your iPhone or in your browser before they sync. Your password never leaves your device.

- 02: Stored only as ciphertext: The server holds encrypted data and nothing else. A stolen disk or backup reveals nothing.

- 03: Entirely yours: You own the server, the domain and the backups, and the keys to your data stay on your own devices.

Built on widely used encryption standards: AES-256 for your data and Argon2 for your password.

### The server sees

- Account names and sign-in times

- How many revisions, their sizes and times

- The names of paired devices

### The server never sees

- Card numbers, expiry, security codes, account numbers

- Notes, tags and card photos

- Your password or any decryption key

An honest boundary: a compromised server could serve modified web code, a limit shared by every browser-based encrypted app. Run the server yourself and keep it updated; on hosts you do not trust, prefer the iPhone app. [Read the threat model](https://github.com/zoolapp/quancard-server/blob/main/THREAT_MODEL.md)

## When edits collide, you decide.

Two devices changed the same card while offline? QuanCard never lets a device clock pick a winner. Identical copies are folded automatically; real differences go to the conflict centre, compared field by field.

- Every differing field is marked; secrets only show "differs"

- Choose per item, or in bulk: most recent edit, one copy of each sample, or keep all as copies

- Every bulk action lists exactly what it will do first

## A real desktop app.

The web vault is not a lite version. It shares card colours and sample data with the iPhone, with interactions built for keyboards and large screens.

### ⌘K command palette

Find cards and accounts, or run an action.

### Sidebar and sheets

Browse by region and favourites; details and edits open in a side sheet.

### Masked by default

Card numbers show the last four digits; full details need your password again.

### Family members

The owner invites; each member has a separate account and a separately encrypted vault.

### Two-step and audit

TOTP with recovery codes, rate limits and lockout, an append-only activity log.

### Open-source server

The sync service and web vault are AGPL-3.0; protocol specs and test vectors are Apache-2.0.

## Three commands. Your own sync service.

You need a Linux host with Docker, a domain pointing to it, and ports 80 and 443 open. One vCPU and 512 MB of memory are enough for a household.

Then open your domain, create the owner account, and pair your iPhone with a scan.

- Get the source: `git clone https://github.com/zoolapp/quancard-server.git && cd quancard-server`

- Write the configuration and a one-time setup token: `./scripts/init-env.sh vault.example.com`

- Start it, with automatic HTTPS certificates: `docker compose up -d --wait`

## About self-hosting

### Is QuanCard open source?

No. The QuanCard iPhone app is a commercial product and its source is not public. Only the self-hosted QuanCard Server is open source: the sync service and the web vault, under AGPL-3.0, with protocol specs and test vectors under Apache-2.0, so you can audit how your data is encrypted and stored.

### Does self-hosting cost anything?

QuanCard Server is free to use, modify and deploy; you pay only for your own server. Pricing for the QuanCard app will be announced separately.

### How is it different from iCloud sync?

iCloud follows your Apple account and needs no upkeep. Self-hosting keeps the data on a server you control and adds the web vault and family accounts. Use one at a time; disconnect before switching, and your local collection stays.

### What if I forget my password?

It cannot be reset: the server never knows your password, which is the price of zero knowledge. A paired iPhone still keeps its local copy. Use a long passphrase and turn on two-step verification.

### What happens if the server is compromised?

The database and backups hold only encrypted data, so a leak reveals no card details. An attacker could alter the web code to capture passwords typed later, so keep the system and image updated, and prefer the iPhone app on hosts you do not trust.

### Can I use only the web, without an iPhone?

Yes. The web vault supports adding, editing and deleting, card photos and routing details, and can be installed as a desktop app (PWA).

### What stage is it at?

A development preview without an independent security audit. Self-hosted sync on iPhone opens with the App Store release. You are responsible for deployment and maintenance.

## Ready to deploy?

The install guide covers quick deployment, reverse proxies, configuration, pairing, backups and upgrades.

Screenshots use the built-in sample data (public test numbers that cannot pay). Card artwork and trademarks belong to their owners.
