Next.js control center
Manage searches, feeds, users, proxy groups, price watches, alerts, and optional account tools.
Open-source Vinted monitoring
Run your own open-source Vinted monitor.
Deploy Vintrack as one observable Docker Compose stack with focused listing monitors, a live dashboard, Discord and Telegram alerts, proxy controls, and optional linked-account tools.
MIT licensed. You remain responsible for deployment security, request policy, data handling, and compliance with third-party terms.
Vintrack stack
docker composeControl center
Next.js dashboard
Monitor worker
Go catalog sessions
PostgreSQL + Redis
State and deduplication
Proxy control
Personal or managed pools
One observable stack, deployed on infrastructure you control.
Infrastructure you control
Keep the dashboard and monitor pipeline in one stack.
Vintrack separates catalog monitoring, account actions, persistence, and live coordination into maintained services without hiding their operational state.
Go monitor workers
Run isolated regional catalog sessions with bounded attempts and Redis-backed deduplication.
PostgreSQL and Redis
Persist application state while coordinating live feeds, caches, and new-listing delivery.
Proxy ownership
Use personal, server-managed, or optional health-checked starter pools by region.
Guided start
Bring up the complete local stack with the repository workflow.
The initializer creates the local environment file, fills missing placeholder secrets, and preserves an existing configuration. Review every production value before exposing the service publicly.
Docker Engine with Docker Compose v2
Git, Make, and OpenSSL
Discord OAuth or an OIDC provider
A public domain and HTTPS for production
terminal
git clone https://github.com/JakobAIOdev/Vintrack-Vinted-Monitor.git vintrack
cd vintrack
make init
docker compose up -d --buildRead the configuration and production deployment guides before opening ports or registering auth callbacks.
Choose the operating model
Try shared infrastructure or own every deployment decision.
Both paths use the same product. The difference is who controls capacity, configuration, users, and ongoing operations.
Capability
Hosted demo
Self-hosted
Setup
Sign in
Deploy and configure
Users and roles
Demo policy
Operator controlled
Proxy capacity
Shared or personal
Operator controlled
Data and backups
Demo managed
Operator controlled
Updates
Automatic
Operator scheduled
Operational boundaries
Transparent control comes with responsibility.
Vintrack documents the boundaries between public catalog monitoring, explicitly authorized account actions, and Vinted's native checkout.
Respect access controls
Do not use Vintrack to bypass authentication barriers, CAPTCHAs, rate limits, or other controls.
Protect deployment secrets
Keep OAuth credentials, proxy passwords, webhooks, session data, and encryption keys out of source and logs.
Set responsible policy
Choose intervals, capacity, retention, users, and linked-account access appropriate for your environment.
Prefer to see the product before deploying it?
The hosted demo exposes the same dashboard workflow with shared-role limits.
FAQ
Straight answers before you start.
Vintrack keeps monitoring, notifications, and account actions separate so you can enable only what you need.
What do I need to self-host Vintrack?
The guided setup expects Docker Engine with Docker Compose v2, Git, Make, and OpenSSL. A public production deployment also needs a domain, HTTPS, and a configured Discord OAuth or OIDC provider.
Can I use my own Vinted proxies?
Yes. Vintrack supports personal and server-managed proxy groups alongside optional shared starter pools. Self-hosted operators control which sources and regional capacity their users can access.
Where does self-hosted Vintrack store data?
The stack uses PostgreSQL for persistent application data and Redis for coordination, caching, deduplication, and live state. You control the host, volumes, backups, secrets, and retention configuration.
How is self-hosting different from the live demo?
The demo is shared, best-effort infrastructure with operator-defined role limits. A self-hosted deployment gives you administrative control over users, proxy capacity, intervals, notifications, domains, and deployment policy.
Inspect the stack, then run it your way.
Read the repository documentation, configure the public origin and authentication carefully, and keep the deployment under your control.