Skip to the article
Aniq-UI

VelraRequirements

Requirements

What to install before you run your package, with Docker or without it.

For the Full Stack package

What each package contains

PackageApps in the downloadRuns on its own
Full StackAPI, public website, agency dashboardYes, all three together
Public WebsitePublic websiteNo: it needs the Velra API running
Agency DashboardAgency dashboardNo: it needs the Velra API running
Backend APIAPIYes, serving the API only

A single-app package does not include the other apps. The website and the dashboard read everything from the Velra API, and the API's code is only in the Full Stack and Backend API packages.

With Docker

  • Docker Desktop on macOS or Windows, or Docker Engine with the Compose plugin on Linux, with Docker Compose 2.24 or newer, which every current Docker Desktop includes; docker compose version prints yours. The full stack starts with one docker compose command, and docker-compose.yml reads back-end/.env only when it exists, a setting older Compose versions reject.
  • An internet connection for the first build, which downloads the base images and the dependencies.
  • Nothing else: Docker brings Node.js, and the database is a SQLite file inside a Docker volume.

With Docker

  • Docker Desktop on macOS or Windows, or Docker Engine on Linux. Your app has its own Dockerfile; Compose is not needed.
  • An internet connection for the first build, which downloads the base image and the dependencies.

Without Docker

  • Node.js 22 or newer, the version every app declares in engines. The Docker images run on Node.js 24. Check yours with node -v.
  • Yarn 4, through Corepack. Run corepack enable once; each app pins its own Yarn version in packageManager, so yarn picks the right one. If your Node.js has no Corepack (Node.js 25 and newer leave it out), install it first with npm install -g corepack.
  • No global packages.

Database

No database server. The API uses SQLite by default and yarn seed creates the file for you; Docker uses SQLite too. MySQL is supported as a configuration change, not a code change.

Ports

Each app listens on a fixed local port. Make sure nothing else uses them, or, with Docker, move one with SITE_PORT, ADMIN_PORT or API_PORT in a .env beside docker-compose.yml.

AppPort
API8000
Public website3030
Agency dashboard3031

Port

The website listens on port 3030 and expects the API on 8000. Make sure nothing else uses them.

Port

The dashboard listens on port 3031 and expects the API on 8000. Make sure nothing else uses them.

Port

The API listens on port 8000, and by default accepts the website from 3030 and the dashboard from 3031. Make sure nothing else uses port 8000.

An API to connect

Your app has no data of its own. It needs the Velra API running and seeded, whose address you set in its .env or pass as a build argument. The API is sold as its own package, the Backend API, and is part of the Full Stack.

Optional services

None of these is needed to run the agency locally. Each is switched on by its variables in the API's .env; a variable left commented out keeps its feature off.

ServiceWithout it
Cloudflare R2 or another S3-compatible bucketUploads are stored on the API's own disk (with Docker, in the data volume), and the API serves the seeded photos itself.
An AI key from Google Gemini, OpenAI or DeepSeek, any oneThe AI assistant says it needs a provider key and lists the three it accepts, and nothing is billed. Everything else works.
A Google Gemini key, for the staging studioThe AI staging studio says it needs one and generates nothing, even when the assistant runs on an OpenAI or DeepSeek key.
A key for the MCP serverPOST /api/mcp refuses every request.

There is no mail or payment service to set up: inquiries and viewing requests arrive as notifications in the dashboard.

Maps

The dashboard's maps draw OpenFreeMap tiles, and the property editor's place search uses the public Photon service. Both need an internet connection and no key or account; neither promises availability, and you can point them at your own services.

Stuck on a step?

Find a fix before you start over.

Troubleshooting

Cookie Preferences

We use cookies to enhance your browsing experience, analyze site traffic, and personalize content. By clicking "Accept All", you consent to our use of cookies for analytics and personalized advertising.