All features
Track & understand
Copy tracking Copy history Custom catalogues NEW Collection insights
Own & collaborate
Data ownership Collaboration Organization Photos & browsing
Protect & extend
Protection & care API Self-hosting Security
Pricing Docs API FAQ GitHub Sign in

Your collection. Your server. Your slightly over-specified NAS.

Keep your collection where you can point at it.

KolleK is built to run on infrastructure you choose. Keep the app, your photos, your documents, and the details of what you own under your control.

Put it on your hardware
Your server
docker compose up

Application

Web Serves the UI and API
Queue worker Background jobs
Scheduler Recurring tasks

State: you own this

Database Encrypted at rest with your application key
Persistent storage Uploaded photos & documents · local or S3

Run it yourself

Your data has an address.

Run KolleK yourself with Docker. Your database and uploaded files live where you decide they live, not behind a vague promise and a login page you hope stays around forever.

Local disk S3-compatible Your own volume MIT licensed
docker-compose.yml
services:
app:
image: kollek:latest
ports: ["${APP_PORT:-8000}:80"]
environment:
APP_KEY: ${APP_KEY}
volumes: [storage-data:/var/www/html/storage]
mysql:
volumes: [db-data:/var/lib/mysql]
# your data. your paths. your call.

Encryption at rest

Sensitive details are not stored as plain text.

KolleK encrypts sensitive fields at rest. Names, values, locations, and item details are protected in the database by your instance’s application key. Curious database thieves get gibberish.

Amazing Spider-Man #300
In the app
Estimated value $6,400
Location Home safe · Shelf 3
Purchase note Bought at auction, 2019
Condition CGC 9.8
items
In the database
value_enc q7Xk9…vT2aZ1pLc8Hh==
location_enc M2fD…uR0bQ9sW4nEy==
note_enc aP5…Lz8Kd3Xmt1oJ7g==
condition_enc Yh1…Ns6Ce0Wq2Bv9d==

Backups

Backups are real, not a decorative button.

A complete backup includes the database, uploaded photos and documents, and your application key. Keep all three. Losing the key would be an extremely bad plot twist.

db-data

The database

Every collection, item, custom field, and history entry: the whole catalogue.

storage-data

Photos & documents

Uploaded files from local disk or S3-compatible storage.

APP_KEY

The application key

Decrypts the encrypted fields. Without it, the backup is gibberish too.

All three, together. Restore into any KolleK instance and you are exactly where you left off.

You are in charge. That is the point.

Self-hosting asks you to own upgrades and backups. In exchange, you get meaningful control over the collection and the system that holds it.

Read the self-hosting guide

You own upgrades

Pull a new image on your schedule, not ours.

You own backups

Real copies of the database, storage, and key.

You own the key

The application key never leaves your instance.

KolleK might not be for you (yet) if…

You do not want any responsibility for hosting, upgrades, or backups.

You need end-to-end encryption where the operator cannot access application data.

You expect an automated in-app backup button.

Choose KolleK when…

You want to decide where the app, data, photos, and documents live.

You want sensitive fields encrypted at rest and control over the encryption key.

You are willing to make real backups of the database, storage, and application key.

The operator holds the encryption key; backups are an operator responsibility. The feature status page has the boring-but-important details.