Question 1

How do I deploy an application from the Marketplace?

Accepted Answer

Choose a Cloud VPS then select the desired template: the environment is installed automatically and accessible from your domain.

Question 2

What is the Marketplace?

Accepted Answer

The Marketplace is a catalog of VPS templates: preconfigured open source applications that you deploy on your VPS in just a few clicks.

Question 3

Are the applications sold by ServOrbit?

Accepted Answer

No. These are open source software programs that we offer as ready-to-deploy templates. You pay for the VPS that hosts them, not for the software.

Question 4

Are the templates free?

Accepted Answer

The applications offered are open source and free. Your only cost is that of the Cloud VPS on which they run.

Question 5

Which applications are available?

Accepted Answer

The catalog covers AI, automation, databases, CMS, deployment and more (88 solutions to date). It is enriched regularly.

Question 6

Can I suggest an application to be added?

Accepted Answer

Yes. Via the contact form, choose "Suggest a solution" and specify the open source application you would like as well as your use case.

Question 7

Why can't I install an application even though my VPS meets the minimum requirements?

Accepted Answer

An application's minimum requirements are stated for an empty server. But your already-installed applications are already consuming part of the RAM, CPU and disk: we therefore check the space actually AVAILABLE on your VPS (and not its total capacity) before launching a new installation, to avoid saturating the machine. If free space is insufficient, increase the resources from your client area (vCPU / RAM / disk options) then restart the installation — or uninstall an application you no longer need.

Question 8

Why is an application marked as "in conflict" or "prerequisite" on my VPS?

Accepted Answer

To guarantee an installation that works the first time, we check compatibility with what is already installed on your server. An application appears blocked in three cases: (1) "port conflict" — it needs the same network port as an application already present (two services cannot listen on the same port of a server); (2) "conflict" — it is a role that can only exist as a single instance, for example two reverse-proxies like Caddy and HAProxy that both want to manage ports 80/443; (3) "prerequisite" — it needs another application to be installed first. In each case, the reason is displayed under the application. To install it anyway: uninstall the conflicting application, install the prerequisite first, or use another VPS.

Question 9

What is Gitea and why self-host it?

Accepted Answer

Gitea is a lightweight, open source Git platform written in Go. Self-hosting it gives you unlimited private repositories, built-in CI/CD (Gitea Actions), a package registry and fine-grained team permissions — all on a 2 GB RAM VPS, with no per-seat billing.

Question 10

Which port does Gitea use on my VPS?

Accepted Answer

Gitea serves its web interface on port 3000 (proxied to 80/443 via Caddy or Nginx). Git over SSH is exposed on port 2222 to avoid conflicting with the VPS host SSH on port 22.

Question 11

Can I use Gitea Actions for CI/CD?

Accepted Answer

Yes. Enable Gitea Actions in your app.ini (`[actions] ENABLED = true`) and register an `act_runner` container on the same VPS. Gitea Actions is compatible with GitHub Actions YAML syntax, so most existing workflows run unchanged.

Question 12

How do I clone a Gitea repository over SSH?

Accepted Answer

Use `git clone ssh://git@:2222//.git`. You can also add a Host block in `~/.ssh/config` to set Port 2222 transparently so that standard Git commands work without specifying the port.

Question 13

What are the minimum VPS resources for Gitea?

Accepted Answer

Gitea runs comfortably on a VPS with 1 vCPU and 2 GB RAM for teams up to 20 users. Add more RAM if you enable local Gitea Actions runners that compile code. Plan at least 20 GB of SSD storage per repository volume.

Question 14

What is PocketBase?

Accepted Answer

PocketBase is an open-source backend-as-a-service (BaaS) written in Go. It bundles an embedded SQLite database, a realtime REST and WebSocket API, built-in authentication (email/password, OAuth2, OTP) and a web admin dashboard in a single binary — no external database server or configuration files required.

Question 15

How much RAM does PocketBase need?

Accepted Answer

PocketBase runs on 512 MB RAM for light workloads. A 1–2 GB VPS handles thousands of daily active users comfortably. Scale up only if you process very large files or run compute-intensive background jobs alongside it.

Question 16

How does PocketBase compare to Firebase or Supabase?

Accepted Answer

PocketBase is far lighter (one binary vs 10+ Docker services for Supabase) and has a fixed VPS cost with no per-read/per-write billing. Firebase and Supabase are better for infinite cloud scale; PocketBase is better for cost-predictable apps under ~1 M daily requests.

Question 17

Which OAuth2 providers does PocketBase support out of the box?

Accepted Answer

PocketBase supports Google, GitHub, GitLab, Apple, Twitter/X, Facebook, Microsoft, Spotify, Kakao, Twitch and more. Enable them in the admin dashboard under Settings → Auth Providers by pasting your OAuth2 client ID and secret.

Question 18

How do I back up my PocketBase data?

Accepted Answer

All data lives in the `/pb/pb_data` Docker volume — one SQLite file plus uploaded files. Back up this volume with `docker run --rm -v pocketbase:/data alpine tar -czf - /data`. PocketBase also exposes a built-in backup endpoint accessible from the admin dashboard.

Question 19

Can I add custom server-side logic to PocketBase?

Accepted Answer

Yes. PocketBase supports JavaScript hooks since v0.17: run code before or after record create, update, delete, or authentication events. For advanced use cases, embed PocketBase as a Go library and add your own HTTP handlers or background jobs.

Question 20

What is Vaultwarden?

Accepted Answer

Vaultwarden is an open-source, unofficial implementation of the Bitwarden server written in Rust. It is 100% compatible with all official Bitwarden clients (browser extensions, iOS, Android, desktop, CLI) and uses under 50 MB RAM — making it ideal for self-hosting on a small VPS.

Question 21

Do I need HTTPS to run Vaultwarden?

Accepted Answer

Yes. Official Bitwarden clients refuse to connect to a server without a valid TLS certificate. You need a domain name and a reverse proxy (Caddy, Nginx, or Traefik) with a Let's Encrypt certificate. Caddy makes this a one-liner — it provisions and renews the cert automatically from your Caddyfile.

Question 22

How much RAM does Vaultwarden need?

Accepted Answer

Vaultwarden idles under 50 MB RAM. A 512 MB VPS is sufficient for personal use or a small team; 1 GB is comfortable for an organization with 20–50 users. It runs easily alongside other services without impacting performance.

Question 23

Can I import my existing passwords into Vaultwarden?

Accepted Answer

Yes. Export your vault from Bitwarden.com (Settings → Export Vault → JSON format) and import it in Vaultwarden's web vault under Tools → Import Data. The process takes under two minutes and preserves all passwords, folders, notes, and identities.

Question 24

How do I prevent strangers from creating accounts on my Vaultwarden instance?

Accepted Answer

Set the environment variable `SIGNUPS_ALLOWED=false` on the container and restart it. New sign-ups will be rejected. You can still invite specific users via the admin panel, which you enable with the `ADMIN_TOKEN` environment variable.

Question 25

How do I back up my Vaultwarden data?

Accepted Answer

All data lives in the `/data` Docker volume: one SQLite file plus file attachments. Run `docker run --rm -v vaultwarden:/data -v /backup:/out busybox tar czf /out/vaultwarden-backup.tar.gz /data` to create a snapshot. Schedule this in cron for automated daily backups.

Question 26

What is Beszel?

Accepted Answer

Beszel is a lightweight open-source (MIT) server monitoring hub. You deploy one hub and install small agents on each server you want to track. The hub aggregates real-time CPU, RAM, disk, bandwidth and Docker container metrics across all your servers in a single PocketBase-backed dashboard.

Question 27

How much RAM does Beszel need?

Accepted Answer

The hub idles under 50 MB RAM and fits comfortably on a 512 MB VPS alongside other services. Agents are even lighter — a few MB each. You can monitor 20+ servers without the hub using more than ~100 MB RAM.

Question 28

Do I need to open firewall ports on monitored servers to use Beszel?

Accepted Answer

No. Beszel agents establish outbound connections to the hub — monitored servers do not need any inbound ports opened. You only need port 8090 (or your HTTPS proxy port) accessible on the hub server itself.

Question 29

What is the difference between Beszel and Uptime Kuma?

Accepted Answer

Uptime Kuma is built for availability checks: is a URL or TCP port up or down? Beszel is built for resource monitoring: CPU, RAM, disk, bandwidth and Docker stats per server. They complement each other — use Uptime Kuma for external blackbox probes and Beszel for internal metrics across your fleet.

Question 30

Can Beszel monitor Docker containers?

Accepted Answer

Yes. Mount `/var/run/docker.sock` when running the agent container and Beszel automatically discovers and tracks all Docker containers on that host — CPU, RAM and network per container, with no extra exporter required.

Question 31

How do I receive alerts in Beszel?

Accepted Answer

Beszel supports email, Telegram, Slack, Discord, ntfy, PagerDuty and Pushover via its built-in notification settings. Define a threshold on any metric (e.g. disk > 80%) and Beszel fires the alert when the threshold is crossed and again when it clears.

Question 32

What is Twenty?

Accepted Answer

Twenty is an open-source CRM (AGPL-3.0) built as a self-hosted alternative to Salesforce and HubSpot. It offers customisable objects and fields, kanban and list views, a GraphQL + REST API, built-in notes and tasks, and a background worker for automations and webhooks. As of v2.1.0 it is production-ready for single-tenant self-hosted deployments.

Question 33

How much RAM does Twenty need?

Accepted Answer

The full Twenty stack (server + worker + PostgreSQL + Redis) idles around 1.2 GB RAM. Plan for 2 GB minimum and 4 GB recommended to give PostgreSQL room under concurrent queries. The server itself uses roughly 300–400 MB at idle.

Question 34

Is Twenty free to self-host?

Accepted Answer

Yes — Twenty is fully open source under AGPL-3.0. Self-hosting on your own VPS is free. There is no per-seat fee, no usage billing and no features gated behind a paid plan on the self-hosted edition. You only pay for the VPS.

Question 35

How does Twenty compare to HubSpot or Salesforce?

Accepted Answer

HubSpot and Salesforce are cloud SaaS products with per-seat billing and your data stored on their infrastructure. Twenty is self-hosted: all data stays on your server, the cost is a flat VPS fee, and you can extend the schema, API and automations without vendor approval or marketplace restrictions.

Question 36

Does Twenty have an API?

Accepted Answer

Yes — every object in Twenty (contacts, companies, deals, and any custom object you define) is accessible via a fully documented GraphQL API and a REST API. Webhooks fire on any record event. The API is the primary integration surface, not an afterthought.

Question 37

Can I import my contacts from HubSpot or Pipedrive into Twenty?

Accepted Answer

Yes. Twenty supports CSV import from workspace settings → Import. Export your contacts and companies as a CSV from HubSpot, Pipedrive or any legacy CRM, then import them into the matching Twenty object. More complex migrations (deals with activity history) may need a short API script.

Question 38

What is Qdrant and why do I need it for RAG?

Accepted Answer

Qdrant is an open-source vector database written in Rust. It stores document chunks as embedding vectors and retrieves the most similar ones in milliseconds. RAG (Retrieval-Augmented Generation) uses this to inject relevant context into each LLM call — so your AI answers from facts instead of hallucinating. A relational database or full-text index cannot match Qdrant's speed or accuracy at this task.

Question 39

How much RAM does Qdrant need?

Accepted Answer

Qdrant idles at around 100–200 MB of RAM. The practical limit is your index size: 1 million 1536-dimensional float32 vectors take roughly 6 GB unquantised, or ~1.5 GB with scalar quantisation (int8). For most small-to-medium RAG projects, a 4 GB VPS is the comfortable starting point.

Question 40

Which embedding models work with Qdrant?

Accepted Answer

Any model that produces fixed-size float vectors. Popular self-hosted choices via Ollama: mxbai-embed-large (1024 dims), nomic-embed-text (768 dims). Via API: OpenAI text-embedding-3-small (1536 dims), Cohere Embed. LangChain, LlamaIndex, Haystack, and the official Qdrant SDKs (Python, TypeScript, Go, Rust) all have native connectors.

Question 41

Can I run Qdrant and Ollama on the same VPS?

Accepted Answer

Yes. Both are single-container deployments with no port conflict (Ollama on 11434, Qdrant on 6333/6334). A 4 GB RAM VPS comfortably runs both with a 7B Q4 model loaded — giving you a fully self-contained, air-gapped RAG stack: embed with Ollama, retrieve with Qdrant, generate with Ollama, no external API needed.

Question 42

Is Qdrant a good Pinecone alternative?

Accepted Answer

Yes. Qdrant is the leading self-hosted alternative to Pinecone. It matches or exceeds Pinecone on benchmark latency and recall, supports the same embedding model ecosystem, and costs a flat VPS fee instead of per-vector and per-query billing. The trade-off: you manage the infrastructure yourself.

Question 43

How do I secure a Qdrant instance?

Accepted Answer

Restart the container with the QDRANT__SERVICE__API_KEY environment variable set to a strong random string. All REST and gRPC requests must then include the `api-key` header. Place Qdrant behind Caddy or Nginx for HTTPS. Never expose port 6333 to the internet without authentication.

Question 44

What is Infisical and why self-host it?

Accepted Answer

Infisical is an open-source secrets manager (MIT, 27.6k stars) — a self-hosted alternative to Doppler and HashiCorp Vault. It centralises API keys, database passwords and certificates in one vault, synced automatically to your apps and CI pipelines via SDKs and native integrations. Self-hosting keeps your most sensitive credentials on your own infrastructure with full audit logs, at a flat VPS cost instead of per-developer SaaS billing.

Question 45

How much RAM does Infisical need?

Accepted Answer

The Infisical stack (app + PostgreSQL 14 + Redis) idles around 600–800 MB of RAM and peaks above 1 GB under concurrent API requests from multiple apps. Plan for a VPS with at least 2 GB RAM (4 GB recommended for teams with several services pulling secrets simultaneously).

Question 46

Does Infisical work with GitHub Actions and GitLab CI?

Accepted Answer

Yes. Infisical has first-class CI/CD integrations: GitHub Actions (official action in the marketplace), GitLab CI (native variables sync), CircleCI and Jenkins. You add a service token as a CI secret, then the integration injects the right environment's secrets directly into each pipeline run — no .env files, no manual rotation.

Question 47

Can Infisical sync secrets to my Node.js or Python app at runtime?

Accepted Answer

Yes. Install the Infisical SDK (`npm install @infisical/sdk` or `pip install infisical-python`) and fetch secrets at startup. Alternatively use the CLI wrapper: `infisical run -- node server.js` injects secrets as environment variables so your app reads them via `process.env` — no SDK integration required, and no secrets ever touch the filesystem.

Question 48

Is Infisical secure for storing production database passwords?

Accepted Answer

Yes. Infisical encrypts every secret value at rest using AES-256-GCM with an `ENCRYPTION_KEY` you generate and control. In transit, all communication is HTTPS. Access is governed by role-based policies, service tokens and machine identities with the principle of least privilege. Every read and write is recorded in the audit log. The MIT core includes all these security features — no paid tier required.

Question 49

What is the difference between Infisical and Vaultwarden?

Accepted Answer

They solve different problems: Vaultwarden is a personal and team password manager (Bitwarden-compatible — human login credentials, browser extensions, mobile apps). Infisical is a secrets manager for machines and code (API keys, database URIs, tokens — consumed programmatically by apps and CI/CD pipelines via SDKs or the CLI). Most teams use both: Vaultwarden for human credentials, Infisical for application secrets.

Question 50

What is Dockge?

Accepted Answer

Dockge is an open-source (MIT) visual manager for Docker Compose stacks, created by Louis Lam — the same developer behind Uptime Kuma. It lets you create, edit, start, stop and monitor all your multi-container applications from a clean web UI on port 5001, without SSH or command-line. It stores every stack as a standard `compose.yaml` file under `/opt/stacks` on your host.

Question 51

How much RAM does Dockge need?

Accepted Answer

Dockge idles under 150 MB RAM and fits on any VPS without impacting the other services running on it. It is built on Node.js with a SQLite database — there are no external databases or caches to provision. A 512 MB VPS can run Dockge comfortably alongside several managed stacks.

Question 52

Can Dockge manage stacks I created manually before installing it?

Accepted Answer

Yes. Place your existing `compose.yaml` files inside subdirectories under `/opt/stacks` (e.g. `/opt/stacks/n8n/compose.yaml`) and Dockge will discover and display them automatically on next load. The file path convention is `//compose.yaml` — any stack already following that layout appears in the UI without any import step.

Question 53

What is the difference between Dockge, Coolify and Dokploy?

Accepted Answer

They solve different scopes: Dockge is a pure Compose manager — it lets you create and manage stacks on the same server it runs on. Coolify and Dokploy are full PaaS platforms with Git integration, automatic SSL, environment promotion and multi-server deployments. Use Dockge when you want a lightweight UI for your hand-crafted stacks; use Coolify or Dokploy when you want git-push-to-deploy and automated SSL out of the box.

Question 54

Is the Dockge web console safe to use?

Accepted Answer

The built-in terminal console was disabled by default in v1.5.0 following a security advisory (GHSA-7vx4-hf96-mqq6). The rest of Dockge — stack management, log streaming, status dashboard — is fully functional without the console. Do not enable it on a public-facing instance. If you need shell access to containers, use a dedicated SSH session instead.

Question 55

How do I update a stack managed by Dockge?

Accepted Answer

Open the stack in the Dockge UI, click Update, then Start. Dockge runs `docker compose pull` followed by `docker compose up -d` under the hood. To update Dockge itself, edit its own `compose.yaml` (under `/opt/dockge` or wherever you installed it), change the image tag if needed, and run `docker compose up -d` from the terminal — or use another Dockge instance to manage it.

Question 56

What is Authelia and what problem does it solve?

Accepted Answer

Authelia is an open-source (Apache 2.0) authentication and authorization gateway. It sits in front of your apps as a forward-auth endpoint on your reverse proxy (Nginx, Caddy, Traefik). Every request is checked against your policy: unauthenticated users are redirected to the Authelia login portal, where you can enforce a password, TOTP, passkeys or any combination. Apps themselves need no changes — Authelia protects them at the infrastructure level.

Question 57

Do I need a domain name to run Authelia?

Accepted Answer

Yes. Authelia's session cookies must be scoped to a domain (`Domain=.yourdomain.com`), and OIDC callbacks and Let's Encrypt certificates require a publicly resolvable FQDN with HTTPS. Authelia cannot function correctly behind a plain IP address. When you deploy through ServOrbit, point an A record to your VPS and enter the domain during setup — the reverse proxy and TLS certificate are configured automatically.

Question 58

How much RAM does Authelia need?

Accepted Answer

Authelia itself idles under 30 MB RAM. Add approximately 20 MB for the Redis session store. Total: under 60 MB for the full authentication stack. A 512 MB VPS is sufficient for personal use; 1 GB is comfortable for a team of 20 or more users.

Question 59

Can Authelia provide SSO for apps like Gitea or Nextcloud?

Accepted Answer

Yes. Authelia is a certified OpenID Connect (OIDC) provider. Register each app as an OIDC client in `configuration.yml` — give it a client ID, a secret and a redirect URI. Then configure the app to use Authelia as its identity provider. Users authenticate once at your auth portal and are silently forwarded to every connected app without re-entering credentials.

Question 60

What MFA methods does Authelia support?

Accepted Answer

Authelia supports TOTP (any authenticator app: Google Authenticator, Ente Auth, Aegis, Bitwarden Authenticator), WebAuthn/Passkeys (Touch ID, Face ID, YubiKey, any FIDO2 hardware key), and Duo push notifications. Users can register multiple methods and choose at login time. MFA is enforced per-domain, per-group or globally depending on your access control rules.

Question 61

What is Actual Budget?

Accepted Answer

Actual Budget is an open-source (MIT), local-first personal finance application built on zero-based (envelope) budgeting. It is a self-hosted alternative to YNAB — you run a lightweight Node.js server on your own VPS and sync your budget to any device through end-to-end encryption. Your financial data never leaves your infrastructure.

Question 62

How does Actual Budget compare to YNAB?

Accepted Answer

The budgeting methodology is identical: assign every dollar to a named envelope (category) before spending it. The differences: Actual is MIT-licensed with no subscription fee, your data stays on your own server, and the source code is fully auditable on GitHub. YNAB has a more polished native mobile app; Actual has a fast PWA and an active open-source community.

Question 63

How much RAM does Actual Budget need?

Accepted Answer

The Node.js server idles under 80 MB RAM. A 1 GB VPS is more than sufficient for multiple simultaneous users. Actual Budget is one of the most resource-efficient self-hosted finance tools available.

Question 64

Can Actual Budget automatically import transactions from my bank?

Accepted Answer

Yes, via two optional integrations: GoCardless for European banks (open banking API, no credential sharing) and SimpleFIN for North American banks. If your bank is not supported, you can import OFX, QFX, QIF or CSV files exported from your online banking portal. Manual transaction logging also works well for cash-flow awareness.

Marketplace

Need help?