Hourly Public Cloud — Brussels from ~€0.0068/h

Understand 1VPS

What is a Debian Linux VPS?

A Linux VPS is an isolated virtual machine: vCPU, RAM and NVMe disk allocated to you, with full root SSH. Unlike shared hosting, you are not limited to a CMS panel or closed ports — install Nginx, Docker, a database, a VPN or your own stack.

Root SSH, packages and services are yours — we provide NVMe, network and panel, not magic managed ops.

• Root SSH, HTML5 console and snapshots from dash.1vps.cc
• Fixed RAM plan: the capacity shown is what you get
• Dedicated IPv4 + AS219084 Anti-DDoS included, no mitigation fee
• Documented bandwidth fair-use — not marketing “unlimited”

Full control, no forced stack

Firewall, reverse proxies, databases, bots, CI runners — SSH or the panel. We provide stable infra; you compose the environment your project actually needs.

Snapshots cover the instance disk state. For busy MySQL/Postgres, a logical dump is still recommended — we prefer saying it clearly.

• apt / dnf and the repos you choose
• Ports opened via your firewall rules
• ISO, reboot and live RAM monitoring
• AS219084 Anti-DDoS on Internet exposure

How do you deploy your Debian VPS?

Three concrete steps: from configurator to a useful first SSH.

1. 1. Select plan and Debian version — Estimate RAM/CPU for your services (site + DB on one machine = more headroom). Pick Debian and the LTS/stable version you want in the OS tab.
2. 2. Wait for provisioning (~1 minute) — After payment / validation, the instance boots automatically. IP, SSH credentials and console access appear in dash.1vps.cc and by email. No manual OS install.
3. 3. Harden, then install your stack — First SSH: change password / key, check panel firewall, create a “clean” snapshot. Then apt/dnf, Nginx, Docker or your stack — like a dedicated. Snapshot again before a critical upgrade.

Which projects fit a Debian VPS?

When shared hosting limits ports, performance or isolation, a Linux VPS is the natural next step.

Concrete cases where Debian is a healthy choice — without claiming a small plan replaces a cluster.

• Sites & reverse proxies — Nginx or Caddy, multiple vhosts, Let’s Encrypt SSL, PHP or static apps behind one proxy.
• APIs & backends — Self-hosted Node, Python, Go or Java services, webhooks and workers on a stable dedicated IP.
• Databases & caches — MariaDB, PostgreSQL or Redis on NVMe — ideal when you split data from the front as load grows.
• Ops & automation — WireGuard VPN, bastion, monitoring, CI runners, Discord bots — the tool that must simply run 24/7.

How do I access my Debian instance?

After deploy you get SSH credentials (IP, user, password or key) by email and in dash.1vps.cc. Connect with a standard SSH client.

Which Debian versions / images are available?

We notably offer: bookworm, bullseye, trixie. More builds may be selectable at deploy time depending on maintained images.

What is a Ubuntu Linux VPS?

A Linux VPS is an isolated virtual machine: vCPU, RAM and NVMe disk allocated to you, with full root SSH. Unlike shared hosting, you are not limited to a CMS panel or closed ports — install Nginx, Docker, a database, a VPN or your own stack.

Root SSH, packages and services are yours — we provide NVMe, network and panel, not magic managed ops.

• Root SSH, HTML5 console and snapshots from dash.1vps.cc
• Fixed RAM plan: the capacity shown is what you get
• Dedicated IPv4 + AS219084 Anti-DDoS included, no mitigation fee
• Documented bandwidth fair-use — not marketing “unlimited”

Full control, no forced stack

Firewall, reverse proxies, databases, bots, CI runners — SSH or the panel. We provide stable infra; you compose the environment your project actually needs.

Snapshots cover the instance disk state. For busy MySQL/Postgres, a logical dump is still recommended — we prefer saying it clearly.

• apt / dnf and the repos you choose
• Ports opened via your firewall rules
• ISO, reboot and live RAM monitoring
• AS219084 Anti-DDoS on Internet exposure

How do you deploy your Ubuntu VPS?

Three concrete steps: from configurator to a useful first SSH.

1. 1. Select plan and Ubuntu version — Estimate RAM/CPU for your services (site + DB on one machine = more headroom). Pick Ubuntu and the LTS/stable version you want in the OS tab.
2. 2. Wait for provisioning (~1 minute) — After payment / validation, the instance boots automatically. IP, SSH credentials and console access appear in dash.1vps.cc and by email. No manual OS install.
3. 3. Harden, then install your stack — First SSH: change password / key, check panel firewall, create a “clean” snapshot. Then apt/dnf, Nginx, Docker or your stack — like a dedicated. Snapshot again before a critical upgrade.

Which projects fit a Ubuntu VPS?

When shared hosting limits ports, performance or isolation, a Linux VPS is the natural next step.

Concrete cases where Ubuntu is a healthy choice — without claiming a small plan replaces a cluster.

• Sites & reverse proxies — Nginx or Caddy, multiple vhosts, Let’s Encrypt SSL, PHP or static apps behind one proxy.
• APIs & backends — Self-hosted Node, Python, Go or Java services, webhooks and workers on a stable dedicated IP.
• Databases & caches — MariaDB, PostgreSQL or Redis on NVMe — ideal when you split data from the front as load grows.
• Ops & automation — WireGuard VPN, bastion, monitoring, CI runners, Discord bots — the tool that must simply run 24/7.

How do I access my Ubuntu instance?

After deploy you get SSH credentials (IP, user, password or key) by email and in dash.1vps.cc. Connect with a standard SSH client.

Which Ubuntu versions / images are available?

We notably offer: noble, jammy, focal. More builds may be selectable at deploy time depending on maintained images.

What is a Windows VPS?

A Windows VPS is a virtual machine with Remote Desktop (RDP). You get a Microsoft environment for ISV software, ERP, .NET stacks or tools that will not run on Linux — on a fixed RAM plan, with IPv4 and AS219084 Anti-DDoS.

The instance is hosted in Brussels. Windows licensing depends on the offer / your own license: we stay transparent instead of promising “unlimited Windows”. You manage Windows Update and hardening.

• RDP + console from the 1VPS panel
• Snapshots before a critical Windows update
• Dedicated IPv4 and AS219084 mitigation included
• RAM plans suited to heavy graphical apps

Windows under your control

Install what your business needs. We stabilize infra; Windows patch management stays yours.

No multi-city compute fail-over: one region (Brussels), AS219084 PoPs in France.

• RDP for graphical admin
• NVMe for fast installs and disks
• Panel snapshots for rollback
• Human support on infrastructure

Windows get-started

From order to first remote desktop, without opaque steps.

1. Pick the plan — Size RAM for your software (ERP and ISVs are often hungry).
2. Deploy Windows image — The instance boots with RDP ready; credentials in the panel / email.
3. Install your stack — Runtimes, ISV licenses, IIS/.NET — admin like a physical server.

Which projects fit a Windows VPS?

Anything that depends on a Microsoft environment or a heavy Windows client.

If your vendor requires Windows Server, a dedicated VPS beats hacking a personal workstation.

• ISV / ERP software — Self-hosted Windows Server apps, user access over RDP or the vendor protocol.
• Remote desktop — Centralized workstations or LOB tools, reachable from multiple sites.
• .NET / IIS stacks — Microsoft sites and services on a stable IP with readable resources.
• QA labs — Reproducible Windows environments for tests before production.

How do I RDP into Windows?

After deploy, open a Remote Desktop client to the provided IP with the Administrator account. Credentials are in dash.1vps.cc and by email.

Is the Windows license included?

Yes. Windows Server licensing is included — no separate Microsoft fees for you to manage.

What is a Docker VPS?

Docker packages an application and its dependencies into a portable, isolated, reproducible container. Whether you build in Node, Python, PHP, Java or Go, the idea is the same: what runs locally should behave the same in staging and production.

On 1VPS, the Docker template gives you Engine ready for Compose, Hub images and multi-service stacks — root/panel, NVMe, AS219084 Anti-DDoS. One node = one plan: this is not managed Kubernetes.

• Isolated containers and reproducible builds
• Ideal microservices, staging and light CI
• Volumes on NVMe, snapshots before a risky pull
• AS219084 mitigation on exposed ports

Orchestrate containers your way

Compose, light Swarm or Portainer: you choose the tool. Private registries, multi-services, env vars — security is yours.

Large images and local builds consume plan CPU/RAM. Size accordingly; do not expect magical horizontal auto-scale on a single VPS.

• Multi-service Docker Compose
• Hub images / private registry
• Instance snapshots before a risky pull
• Exposed ports behind your firewall

How do you deploy Docker in practice?

From template to the first `docker compose up`.

1. 1. Take a plan with RAM headroom — Images + running containers + builds eat memory fast. For a multi-service Compose (API, DB, reverse-proxy), do not start on the smallest plan.
2. 2. Deploy the Docker template — OS tab → Docker. Once ready, SSH or panel console, check `docker version`, place your `compose.yml`.
3. 3. Stack, volumes, exposure — Compose up, named volumes on NVMe, reverse-proxy (Caddy/Traefik/Nginx), DNS + TLS. Snapshot before a major image upgrade; watch RAM usage.

What projects fit Docker?

Whenever you want the same stack in local, staging and prod.

Docker on a VPS remains a single node. Multi-node orchestration, clusters or mesh are a different product.

• Web + DB stack — App, reverse-proxy and database as separate Compose services.
• Isolated staging — Recreate prod in one command for QA or client demos.
• Workers & queues — Redis queues, async workers, cron containers.
• Self-host toolbox — Portainer, monitoring, internal tools versioned in Git.

How do I access my Docker instance?

After deploy you get SSH credentials (IP, user, password or key) by email and in dash.1vps.cc. Connect with a standard SSH client.

Which Docker versions / images are available?

We notably offer: ce, compose, buildx. More builds may be selectable at deploy time depending on maintained images.

What is an Nginx + PHP stack?

Nginx + PHP is the classic dynamic web base: a fast HTTP reverse-proxy/server (Nginx) and a PHP runtime (FPM) to run custom WordPress, Laravel, Symfony, Composer apps or scripts. No forced CMS: you drop your code.

On 1VPS, the Nginx + PHP template is one-click on a fixed RAM plan and NVMe. Ideal when a prefab CMS is too rigid, or for a custom PHP front. AS219084 Anti-DDoS included; SSL / Composer per template.

• Nginx + PHP-FPM ready for vhosts
• Compatible with Laravel, Symfony, Composer apps
• Dedicated IP, clear RAM plan
• Snapshots before PHP upgrades or risky deploys

How do you deploy Nginx + PHP?

From plan to the first served index.php.

1. 1. Size for the PHP app — Light site / landing: entry plan. Laravel with queues, many uploads or heavy admin: more RAM. Also plan space for vendor/ and storage.
2. 2. Launch the Nginx + PHP template — Web tab → Nginx + PHP. In ~60s the stack is ready. Get the IP, webroot paths and panel access from dash.1vps.cc.
3. 3. Code, Composer, DNS, SSL — Deploy code (Git/SFTP), `composer install` if needed, configure vhost/document root, DNS A + HTTPS. Wire the DB (MariaDB/PostgreSQL) and take a baseline snapshot.

What projects fit Nginx + PHP?

Whenever you want a PHP web stack without a forced CMS.

For a turnkey blog, WordPress is faster. Nginx + PHP shines for custom code and frameworks.

• Laravel / Symfony app — API or back-office with Composer and .env.
• Custom PHP site — Legacy or homemade, clear document root.
• Framework staging — Recreate a near-prod environment.
• PHP micro-SaaS — Small business app behind Nginx + SSL.

How is the Nginx + PHP offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the Nginx + PHP stack?

Yes. Versions and components (e.g. nginx, apache, php83) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is WordPress hosting?

WordPress hosting is an environment built to run the CMS properly: PHP, database, site files and admin access — without assembling a full LEMP stack by hand. The goal: publish, customize and grow a site without starting from scratch every time.

On 1VPS, WordPress is a one-click template on a fixed RAM plan. You stay admin (plugins, themes, updates): we speed up the start, without “magic” managed WordPress.

• WordPress ready in about 60 seconds after order
• File / DB access per offer; panel snapshots before risky updates
• Dedicated IP, clear RAM plan — ideal once shared hosting saturates
• AS219084 mitigation included; documented fair-use bandwidth

How do you deploy WordPress step by step?

The real flow after order — what you do, and what the panel does for you.

1. 1. Pick the plan for the real site — Brochure / light blog: an entry plan can work. WooCommerce, heavy page builders, many plugins or traffic: take more RAM from day one. Better one tier up than an admin that times out.
2. 2. Launch the WordPress template — In the web tab, select WordPress and confirm. In ~60 seconds the stack (files, PHP, DB per offer) is ready. You get the admin URL, panel access and useful info in dash.1vps.cc.
3. 3. Domain, content, then harden — Point your domain (DNS A to the IP), sign in to wp-admin, install only essential theme/plugins. Enable SSL per template, take a first snapshot before big changes, and plan application backups.

What projects fit WordPress?

From a personal blog to a WooCommerce store — whenever you want a dedicated IP and predictable resources.

WordPress stays versatile — just size the plan for reality (cache, images, extensions).

• Brochure site — SMBs, associations, freelancers: a few polished pages, contact form, solid baseline SEO.
• Blog & media — Regular editorial content, SEO, newsletters — with enough RAM for admin and object cache.
• WooCommerce — Online store: catalog, cart, payments. Plan more RAM and a cache strategy from day one.
• Multisite / agency — Several sites or client staging on one clear plan model — without opaque shared hosting.

How is the WordPress offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the WordPress stack?

Yes. Versions and components (e.g. wpcli, php83, nginx) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is Nextcloud hosting?

Nextcloud is your personal cloud: files, calendars, contacts, team sharing and collab apps — under your control, not a consumer drive. Nextcloud hosting provides the stack (app + storage + admin) so you can self-host without building the install by hand.

On 1VPS, Nextcloud is a one-click template on a fixed RAM plan and NVMe. You manage users, apps and quotas; we provide the instance, dedicated IP and AS219084 mitigation. Ideal once Dropbox/Google Drive no longer fit (GDPR, sovereignty, teams).

• Files, desktop/mobile sync and external shares
• Nextcloud apps (calendar, Talk, OnlyOffice depending on your stack)
• NVMe storage — size for your data volume
• You keep control of accounts and permissions

How do you deploy Nextcloud in practice?

From plan to first client sync — the steps that actually matter.

1. 1. Size RAM and disk for the data — Few users / few GB: an entry plan can work. Heavy sync, previews, Talk or a large media library: take more RAM and enough NVMe. Nextcloud likes memory headroom.
2. 2. Launch the Nextcloud template — Web tab → Nextcloud → confirm. In ~60s the instance is ready. Get the URL, initial admin account and IP from dash.1vps.cc. Save credentials immediately.
3. 3. Domain, HTTPS, users, clients — DNS A to the IP, HTTPS per template, create accounts, install desktop/mobile clients. Enable only useful apps, snapshot before a major upgrade, and plan data backups (not only disk snapshots).

What projects fit Nextcloud?

Anything that needs a private drive, light collab and data ownership.

Nextcloud is not multi-site enterprise NAS: it is an excellent personal / SMB cloud on a clear plan. For multi-node HA, talk to us first.

• Team drive — Folder sharing, group rights, external links with expiry — without a US SaaS.
• Personal self-hosting — Photos, documents, calendar: your backup copy and multi-device sync.
• Practice / association — Sensitive documents, named access, simple share auditing.
• Light collab — Day-to-day editing and sharing; wire OnlyOffice/Collabora if your stack allows.

How is the Nextcloud offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the Nextcloud stack?

Yes. Versions and components (e.g. 30, 29, 28) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is a GitLab VPS?

GitLab CE combines Git forge, CI/CD, registry and many DevOps tools in one suite. A GitLab VPS starts that stack for teams that want a self-hosted alternative to GitLab.com / GitHub Enterprise.

On 1VPS, GitLab is a one-click template — but GitLab is heavy: plan generous RAM (often 8GB+ in real use with runners). NVMe and AS219084 included; administration (upgrades, omnibus backups) stays yours.

• Git + Merge Requests + CI pipelines
• Container Registry depending on your config
• RAM plan: do not underestimate GitLab
• Omnibus backups / snapshots before upgrades

DevOps suite under your roof

Projects, groups, runners, CI variables, protected branches: the full GitLab model, at home.

Runners co-located on the same machine as GitLab step on each other. Split them when CI gets serious.

• `.gitlab-ci.yml` pipelines
• Dedicated runners recommended
• SSO / LDAP depending on your build
• Artifact retention policy

How do you deploy GitLab without surprises?

The classic trap: a plan that is too small. Start roomy.

1. 1. Pick a comfortable plan — GitLab + Sidekiq + PostgreSQL + Redis eat RAM quickly. For a real team, skip the entry tier. Leave headroom for CI spikes.
2. 2. Launch the GitLab template — Software tab → GitLab. First boot can take longer than a CMS. Watch the panel until the UI is up, then change the root password.
3. 3. Domain, runners, backup — DNS + TLS, create groups/projects, add a runner (ideally elsewhere), configure omnibus backup + disk snapshot. Document the restore procedure.

What projects fit GitLab?

Teams that want Git + CI in the same product.

For only hosting light Git repos, Gitea is leaner. GitLab is worth it once CI/CD is central.

• Software product — MRs, reviews, test and deploy pipelines.
• Internal platform — Monorepo or multi-projects with group permissions.
• Continuous delivery — Build → registry → deploy to your targets.
• Compliance / on-prem — Code and runners inside your perimeter.

How is the GitLab VPS offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the GitLab VPS stack?

Yes. Versions and components (e.g. ce, runner, registry) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is an OpenVPN VPS?

OpenVPN creates an encrypted tunnel between your devices and a server: secure remote access, bypassing local filters, or a bastion to administer internal resources. OpenVPN hosting provides an instance ready to issue client configs.

On 1VPS, OpenVPN is a one-click template on a fixed RAM plan. You manage certificates, users and routes; we provide NVMe, dedicated IP and AS219084 mitigation on the exposure. This is not a consumer “unlimited anonymous VPN”: it is your gateway.

• Encrypted client ↔ server tunnel under your control
• .ovpn configs to distribute to your team
• Stable dedicated IP for remote ACLs and firewalls
• You remain responsible for access and security policy

Control routes and access

Split-tunnel or full-tunnel, named users, certificate revocation: you define the policy. No marketing black box.

A VPN does not excuse bad practice: MFA on services behind it, least privilege, and credential rotation stay on you.

• Windows, macOS, Linux, mobile clients
• Immediate revocation of a lost access
• Panel firewall to open only what is needed
• Snapshots before a PKI change

How do you deploy OpenVPN?

From plan to the first client connection.

1. 1. A light plan is often enough — OpenVPN is light on RAM for a few tunnels. Raise the plan for many concurrent clients or heavy routed traffic.
2. 2. Launch the OpenVPN template — Software tab → OpenVPN. Get admin/panel info, generate or download client configs per template.
3. 3. Clients, tests, hardening — Import the .ovpn, test connectivity, restrict ports, document who has access. Baseline snapshot after a stable config.

What is OpenVPN for?

Pro remote access, bastion and team networks.

Follow the law and network ToS. A VPN is not a tool to abuse fair-use or hide malicious traffic.

• Remote work — Employees / freelancers joining an application LAN.
• Admin bastion — SSH/RDP to machines only through the tunnel.
• Multi-office sites — Link two small sites (per your network design).
• Lab / staging — Private environments reachable without exposing everything to the internet.

How is the OpenVPN VPS offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the OpenVPN VPS stack?

Yes. Versions and components (e.g. 2.6, 2.5, udp) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is a Pterodactyl VPS?

Pterodactyl is a game-server panel: web UI, RAM/CPU allocations, eggs (Minecraft, Steam…) and Wings on nodes. Ideal to host several game servers cleanly, without hacky SSH scripts.

On 1VPS, one-click Pterodactyl template. Note: panel + Wings + games consume resources — take a roomy plan and read egg docs. AS219084 Anti-DDoS helps on exposed game ports. This is not a magic Minecraft server: it is the platform to manage them.

• Web panel to manage multiple game servers
• Community eggs (MC, Steam, etc.)
• RAM/CPU allocations per server
• Wings + Docker under the hood

Game ops under control

Nodes, locations, users, per-server databases: the full Pterodactyl model. Add more nodes when you scale.

A panel too small for the games it hosts = queues and OOM. Sometimes split panel and node.

• Panel users and permissions
• Schedules, game backups
• Network / port allocations
• Snapshots before panel upgrades

How do you deploy Pterodactyl?

Panel → Wings node → first egg.

1. 1. Roomy plan from day one — Panel alone is reasonable; panel + games on the same machine needs headroom. List games and their recommended RAM.
2. 2. Launch the Pterodactyl template — Software tab → Pterodactyl. Finish admin setup (user, keys), verify Wings.
3. 3. Eggs, servers, DNS — Add eggs, create the first game server, open ports, invite users. Snapshot after a healthy baseline.

What is Pterodactyl for?

Community hosts and game-server networks.

For a single Minecraft without a panel, a dedicated game template may be enough. Pterodactyl shines once you manage several.

• Minecraft network — Survival, creative, lobby — separate allocations.
• Multi-game — MC + Steam games on the same panel.
• Community / club — Staff with limited rights per server.
• Small host — Resell slots (within game ToS).

How is the Pterodactyl VPS offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the Pterodactyl VPS stack?

Yes. Versions and components (e.g. panel, wings, docker) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is PrestaShop hosting?

PrestaShop is an open-source e-commerce platform: catalog, cart, orders, payments, carriers and merchant back-office. PrestaShop hosting provides PHP, database and files ready to launch a store without installing the stack by hand.

On 1VPS, PrestaShop is a one-click template on a fixed RAM plan. You manage modules, theme and catalog; we provide NVMe, dedicated IP and AS219084 Anti-DDoS. A real store (images, cache, traffic spikes) often needs more RAM than a brochure site.

• Store + back-office ready after deploy
• Payment / shipping modules under your responsibility
• Dedicated IP — useful for DNS, SSL and mail reputation
• Snapshots before PrestaShop or critical module upgrades

How do you open a PrestaShop store?

From sizing to the first published product.

1. 1. Pick a plan built for commerce — Light catalog / MVP: mid plan. Many variants, HD images, heavy modules or sales peaks: raise RAM. PrestaShop admin is hungry — do not under-size “just to test in prod”.
2. 2. Deploy the PrestaShop template — Web tab → PrestaShop. In ~60s the store is provisioned. Get the back-office URL, IP and access from the panel. Change the admin password immediately.
3. 3. Store setup, payments, SSL, backups — DNS, SSL, currency/VAT, carriers, payment modules. Import the catalog, test a full checkout, use maintenance mode while configuring, and plan DB + file backups.

What projects fit PrestaShop?

Whenever you sell online with a real merchant back-office.

PrestaShop shines for classic retail. For a simple Stripe link or tiny catalog, WooCommerce / a lighter stack may be enough.

• SMB store — Structured catalog, stock, orders and basic invoicing.
• D2C brand — Polished theme, checkout funnel, coupons and upsells.
• Multi-currency / EU — Cross-border sales with tax rules and carriers that fit.
• Light marketplace — Extensions and modules as needed — you stay in charge of choices.

How do I deploy PrestaShop?

Pick the PrestaShop egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize PrestaShop?

Yes — files, variables and console are available from the Jexactyl panel.

What is Drupal hosting?

Drupal is a CMS built for structured content, fine-grained permissions and institutional / media sites. Drupal hosting prepares PHP, database and files so you can start a project without rebuilding the stack in every environment.

On 1VPS, Drupal is a one-click template on a fixed RAM plan. You drive modules, themes and Composer deploys; we provide NVMe infra and AS219084. Drupal likes RAM — especially with many entities or a cold cache.

• Powerful CMS for structured content and multisite
• Permissions, editorial workflows, APIs depending on your build
• Clear RAM plan for PHP-FPM / DB
• Snapshots before core / module upgrades

How do you deploy Drupal step by step?

From plan to the first useful content type.

1. 1. Estimate complexity and traffic — Simple editorial site: mid plan. Many content types, media, Solr or audience spikes: more RAM. Also plan space for public/private files.
2. 2. Launch the Drupal template — Web tab → Drupal. ~60s provisioning, then admin / panel access. Secure uid 1 and note the IP.
3. 3. Config, theme, cache, backups — DNS + SSL, enable essential modules, configure cache (page/dynamic), import config if you use a Git workflow, snapshot before prod, regular DB backups.

What projects fit Drupal?

When content structure and permissions matter more than a turnkey theme.

For a simple blog, WordPress is often faster to launch. Drupal shines once the data model gets complex.

• Institutional site — Pages, news, documents, strict editorial roles.
• Media / magazine — Sections, authors, taxonomies and article volume.
• Member portal — Authenticated areas, fine permissions, forms.
• Headless / API — Drupal as a content backend for a decoupled front.

How do I deploy Drupal?

Pick the Drupal egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Drupal?

Yes — files, variables and console are available from the Jexactyl panel.

What is Joomla hosting?

Joomla is a versatile CMS: articles, menus, modules, extensions and native multilingual. Joomla hosting delivers PHP + database + files so you can publish without installing Apache/Nginx/MySQL by hand.

On 1VPS, Joomla is a one-click template on a fixed RAM plan. You choose extensions and template; we provide NVMe, IP and AS219084. Less “opinionated” than WordPress on ecosystem, very flexible on menu structure.

• CMS + admin ready in ~60s
• Extensions and templates under your control
• Strong fit for multilingual / portals
• Snapshots before Joomla or extension upgrades

How do you deploy Joomla?

Three steps from plan to go-live.

1. 1. Pick the plan for extensions — Simple site: entry / mid. Many extensions, galleries or community features: more RAM. Avoid stacking redundant extensions on day one.
2. 2. Launch the Joomla template — Web tab → Joomla → confirm. Get admin access, change the password, note the IP in the panel.
3. 3. Structure, template, SSL, backups — DNS, SSL, menus/categories, template, essential extensions. Baseline snapshot, then regular DB and images-folder backups.

What projects fit Joomla?

Structured sites, multilingual, association or SMB portals.

If you mainly want the WordPress plugin ecosystem, stay on WordPress. Joomla remains a strong choice for complex menus and multilingual.

• Association site — News, pages, documents and volunteer roles.
• Multilingual — Several native languages without a plugin factory.
• SMB portal — Rich menus, business modules, light intranet.
• Magazine — Categories, authors, editorial highlights.

How do I deploy Joomla?

Pick the Joomla egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Joomla?

Yes — files, variables and console are available from the Jexactyl panel.

What is a Next.js VPS?

Next.js is the React framework for modern sites and apps (SSR, SSG, API routes, App Router). A Next.js VPS gives you a Node runtime ready to build and serve your app — without configuring Node/npm from scratch.

On 1VPS, the Next.js template starts on a fixed RAM plan. You deploy your code (Git, CI, or copy); we provide the NVMe instance, IP and AS219084. This is not managed Vercel: you control process, env and reverse-proxy.

• Node / Next ready for SSR and API routes
• Ideal modern front, dashboards, dynamic marketing sites
• Environment variables and processes under your control
• Size RAM for build + runtime

How do you ship a Next.js app to prod?

From plan to `next start` (or an equivalent process manager).

1. 1. Plan RAM for build and runtime — `next build` can spike memory. Light marketing sites: mid plan. Heavy apps, aggressive ISR or many concurrent users: raise RAM.
2. 2. Deploy the Next.js template — Web tab → Next.js. Once the instance is ready, connect (SSH/panel), clone the repo, install deps, configure `.env` secrets.
3. 3. Build, process, domain, observability — Production build, run via PM2/systemd/docker as you prefer, DNS + reverse-proxy/SSL, logs and auto-restart. Snapshot before a major release.

What projects fit Next.js?

Modern web apps where React + SSR/SSG matter.

For a classic PHP blog, WordPress stays simpler. Next.js shines when you want a polished front and co-located APIs.

• Dynamic marketing site — Fast pages, SSR SEO, forms and a headless CMS wired in.
• SaaS / dashboard — React UI, auth, API calls on the same node or to your services.
• Headless storefront — Next.js front wired to Shopify, Medusa, Strapi…
• Product POC — Iterate fast on a clear plan, without edge vendor lock-in.

How do I deploy Next.js?

Pick the Next.js egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Next.js?

Yes — files, variables and console are available from the Jexactyl panel.

What is a Jellyfin server?

Jellyfin is an open-source media server: movies, shows, music, photos — streamed to TVs, browsers or apps. Jellyfin hosting provides an instance ready to scan your library and serve streams, without a proprietary cloud account.

On 1VPS, Jellyfin is a one-click template on NVMe. The bottleneck is usually storage and transcoding: pick a plan with enough disk (and CPU/RAM if you transcode a lot). AS219084 Anti-DDoS on the web exposure.

• Self-hosted media library, no SaaS subscription
• Official clients / browser / TV
• NVMe for metadata and smooth playback
• You bring (and keep owning) your media files

How do you get Jellyfin running?

From plan to the first movie on the couch.

1. 1. Size disk (and transcoding) — The library uses most of the volume. Direct play uses little CPU; 4K multi-stream transcoding needs far more resources. Be realistic about library size.
2. 2. Deploy the Jellyfin template — Web tab → Jellyfin. Create the admin account on first login, note the URL and panel IP.
3. 3. Libraries, users, reverse-proxy — Add media folders (upload, mount, rsync…), run the scan, create users, expose via domain + HTTPS. Snapshot before major upgrades; media backups stay your responsibility.

What is Jellyfin for?

Private streaming for a household, friends or a small community.

Respect copyright: Jellyfin serves your legitimate content. It is not a piracy host.

• Family media library — Ripped / purchased movies and shows at home and on the go.
• Photos & memories — Centralized albums with named access.
• Music — Self-hosted audio library, playlists and client apps.
• Friends circle — A few remote accounts — size bandwidth and fair-use.

How do I deploy Jellyfin?

Pick the Jellyfin egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Jellyfin?

Yes — files, variables and console are available from the Jexactyl panel.

What is phpMyAdmin?

phpMyAdmin is the reference web UI for MySQL / MariaDB: browse tables, run SQL, import/export dumps, manage users and privileges — without a heavy desktop client. Useful for admin, migration and debug.

On 1VPS, phpMyAdmin is a one-click template. Pair it with a MariaDB (or MySQL) VPS. Harden the UI strongly (HTTPS, password, ideally IP allowlist / VPN): it is privileged access to your data.

• Browser UI for MySQL / MariaDB
• SQL and CSV import / export
• User and privilege management
• Harden from the first login

How do you deploy phpMyAdmin?

Admin UI → connect to your SQL server.

1. 1. Have your database first — Deploy or point to MariaDB/MySQL (local or remote). Note host, port, user, password. A small plan is often enough for the UI alone.
2. 2. Launch the phpMyAdmin template — Web tab → phpMyAdmin. In ~60s the UI is ready. Change default access immediately.
3. 3. HTTPS, allowlist, best practices — DNS + TLS, restrict network access, create a least-privilege SQL user for the UI (not root in prod). Snapshot after a stable config.

What is phpMyAdmin for?

Visual SQL admin, migrations and rescue.

It is not a substitute for versioned migrations (Flyway, Doctrine…). It is the day-to-day ops / debug tool.

• CMS admin — Inspect/repair a WordPress or PrestaShop DB.
• Imports / exports — SQL dumps for migration or manual backup.
• Query debug — Test a SELECT, check indexes and data.
• SQL user management — Create app accounts with minimal rights.

How do I deploy PhpMyAdmin?

Pick the PhpMyAdmin egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize PhpMyAdmin?

Yes — files, variables and console are available from the Jexactyl panel.

What is a MariaDB VPS?

MariaDB (MySQL fork) powers much of the PHP web: WordPress, PrestaShop, Laravel apps… A MariaDB VPS gives you a dedicated SQL engine, with InnoDB, users and databases isolated from noisy shared neighbors.

On 1VPS, one-click MariaDB template on NVMe. Perfect alongside an app VPS, or to centralize several small schemas. RAM and disk drive performance; do not expose 3306 publicly without an allowlist.

• Compatible with MySQL / PHP ecosystem
• Dedicated databases and users per application
• NVMe for data + binlogs
• Regular dumps + snapshots

SQL under your responsibility

Charset, collation, indexes, slow query log: you can investigate. No mysterious “max connections” from a saturated shared host.

A bad query can saturate the instance. Monitoring + indexes > endlessly buying RAM.

• mysqldump / backup tools
• Per-app users, minimal privileges
• Firewall allowlist
• Planned minor upgrades

How do you deploy MariaDB?

Engine → schemas → connected apps.

1. 1. Size for tables and QPS — Light blog: small/mid. Large WooCommerce or many joins: more RAM.
2. 2. Launch the MariaDB template — DB tab → MariaDB. Secure root, create DB + app user.
3. 3. Wire apps and backups — JDBC/DSN URL from your app VPS, test, enable nightly dumps, weekly snapshot.

What projects fit MariaDB?

The natural companion for PHP web and CMS.

For very flexible JSON or heavy analytics, PostgreSQL/Mongo may fit better.

• WordPress / CMS — Dedicated DB away from a saturated web container.
• E-commerce — PrestaShop, Woo, large catalogs.
• Laravel / Symfony apps — Classic SQL, Eloquent/Doctrine migrations.
• Multi-sites — Several schemas on one controlled instance.

How do I deploy MariaDB?

Pick the MariaDB egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize MariaDB?

Yes — files, variables and console are available from the Jexactyl panel.

What is a PostgreSQL VPS?

PostgreSQL is the open-source SQL reference: ACID transactions, JSONB, extensions, strong read/write performance when the schema is healthy. A PostgreSQL VPS starts the DB instance for your apps — without opaque shared hosting.

On 1VPS, one-click PostgreSQL template on NVMe. You administer roles, databases, extensions; we provide the RAM plan (critical for shared_buffers) and AS219084 if you expose the port (ideally: do not — use a tunnel/VPN).

• PostgreSQL managed… by you, on a clear plan
• NVMe for WAL and data files
• Roles, schemas, extensions (pg_trgm, etc.)
• Never expose 5432 without hardening

Actually administer the database

Light tuning, vacuum, indexes, logical replicas later if needed — you are not in a capped “DB as a service” black box.

Without monitoring, a DB fills the disk. Plan alerts (Uptime Kuma / exporters) and PITR or regular dumps.

• pg_dump / scheduled backups
• Least-privilege users
• Firewall: IP allowlist
• Snapshots before major upgrades

How do you deploy PostgreSQL?

Instance, app users, restricted network access.

1. 1. RAM = DB performance — Memory drives the cache. Serious apps: skip the smallest plan. Also estimate disk growth.
2. 2. Launch the PostgreSQL template — DB tab → PostgreSQL. Note the superuser password, create a dedicated DB + app user.
3. 3. Access, apps, backups — Allow only app IPs, wire DATABASE_URL, enable dumps/snapshots. Test a restore once.

What projects fit PostgreSQL?

Any app that needs reliable SQL.

For cache or sessions, look at Redis. For large documents, Mongo may fit. PostgreSQL remains the healthy default.

• SaaS / API — Relational schema, Flyway/Prisma/Django migrations.
• CMS / e-commerce — Backend for Woo, Presta, custom apps.
• Light analytics — JSONB, materialized views, exports.
• Multi-apps — One DB per service on the same instance (with discipline).

How is the PostgreSQL offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the PostgreSQL stack?

Yes. Versions and components (e.g. 17, 16, 15) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is a MongoDB VPS?

MongoDB stores flexible JSON/BSON documents: ideal when the schema evolves fast (Node apps, heterogeneous catalogs, events). A MongoDB VPS starts the engine for your apps, without forced Atlas.

On 1VPS, one-click MongoDB template on NVMe. You manage users, replica set later if needed; we provide RAM (WiredTiger loves memory) and a protected network. Do not open 27017 to the whole world.

• Flexible documents, secondary indexes
• Very common with Node / Nest / Meteor stacks
• RAM + disk = WiredTiger performance
• Auth + network allowlist mandatory

Documents under control

Collections, optional schema validation, aggregations: Mongo power without the surprise bill of a managed cluster too early.

Without proper indexes, Mongo “scans everything”. Explain your queries before buying hardware.

• Mongo users and roles
• mongodump backups / snapshots
• Strict firewall
• Monitor connections / disk

How do you deploy MongoDB?

Engine → auth → application URI.

1. 1. Plan for RAM — Working set in memory = happiness. Small projects: mid. Large volumes: raise frankly.
2. 2. Launch the MongoDB template — DB tab → MongoDB. Enable auth, create an app user, note the URI.
3. 3. Wire the app and back up — IP allowlist, connection string in the app, CRUD test, scheduled dumps, snapshot.

What projects fit MongoDB?

Document data and fast iteration.

For strict relational accounting, PostgreSQL is often simpler. Mongo shines on flexibility and JSON.

• Node API — Mongoose / native driver, evolving schemas.
• Product catalogs — Attributes that vary by category.
• Event logs — Event documents, TTL indexes.
• Product POC — Iterate the model without heavy SQL migrations.

How do I deploy MongoDB?

Pick the MongoDB egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize MongoDB?

Yes — files, variables and console are available from the Jexactyl panel.

What is a Redis VPS?

Redis is an in-memory store: cache, sessions, queues, rate-limit, pub/sub. Ultimate for speeding up a web app or decoupling workers. A Redis VPS gives you a dedicated instance, not a “best effort” shared Redis.

On 1VPS, one-click Redis template. RAM IS the database: pick the plan for your key volume. RDB/AOF persistence per your loss tolerance. Never expose Redis without password + allowlist.

• Ultra-fast cache and sessions
• Queues (Bull, Sidekiq, Celery/Redis…)
• RAM plan = max dataset size
• Auth + bind/firewall mandatory

Memory under control

TTL, eviction policies, structures (strings, hashes, streams): you choose the patterns. Redis is not a SQL substitute.

Without TTL, Redis grows until OOM. Design keys with expiry from day one.

• maxmemory policy
• Persistence per criticality
• Redis 6+ ACL if needed
• Monitor hit ratio / memory

How do you deploy Redis?

Hardened instance → URL in the app.

1. 1. Estimate cache size — A few sessions: small plan. Large page cache / jobs: align RAM with the working set.
2. 2. Launch the Redis template — DB tab → Redis. Set requirepass, verify bind.
3. 3. Wire and observe — REDIS_URL in the app, PING test, memory alerts, optional snapshot (per persistence).

What is Redis for?

Speed up and decouple — not replace your primary DB.

Long-lived critical data: PostgreSQL/MariaDB. Redis for speed and queues.

• Application cache — Pages, fragments, expensive query results.
• Sessions — Horizontally scalable web auth.
• Job queues — Async workers, retries, delays.
• Rate limiting — API protection and simple anti-abuse.

How is the Redis offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the Redis stack?

Yes. Versions and components (e.g. 7.4, 7.2, 6.2) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is Gitea hosting?

Gitea is a lightweight Git forge: repositories, issues, PRs, packages depending on config — a self-hosted alternative to GitHub/GitLab for teams that want to own their code. Gitea hosting provides a ready instance without installing Go/Git by hand.

On 1VPS, Gitea is a one-click template on NVMe. You administer orgs, permissions and optional runners; we provide the RAM plan, IP and AS219084. Lighter than full GitLab CE — ideal for SMBs / serious side projects.

• Git + web UI for review and collaboration
• Low RAM footprint vs a “full enterprise” forge
• Git SSH and HTTPS under your domain
• Snapshots before Gitea upgrades

Your forge, your rules

Private/public repos, teams, webhooks, mirrors: you decide. Wire external CI (Woodpecker, self-hosted Actions, etc.) if needed.

Large LFS / artifacts need disk: size NVMe, do not store huge binaries “by habit”.

• Permissions per organization / repo
• SSH keys and access tokens
• Webhooks to your CI
• Backup of repos + DB

How do you deploy Gitea?

From template to the first `git push`.

1. 1. Plan for team and CI — A few repos: entry/mid. Many mirrors, co-located CI or LFS: more RAM/disk.
2. 2. Launch the Gitea template — Software tab → Gitea. Create the admin account, set the root URL (domain), note the IP.
3. 3. DNS, Git SSH, users, backup — DNS + TLS, open the Git SSH port if needed, invite the team, disable open registration, plan DB + repository backups.

What projects fit Gitea?

Private code, internal forge, light GitHub alternative.

If you want a full DevOps suite (heavy built-in CI, registry, etc.), also look at GitLab. Gitea wins on simplicity.

• Product team — Repos, PRs, issues daily without an external SaaS.
• Agency / freelancers — One repo per client, separated permissions.
• Git mirror / backup — Mirrors of critical repos off GitHub.
• Inner source — Internal company forge with SSO via your tools.

How do I deploy Gitea?

Pick the Gitea egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Gitea?

Yes — files, variables and console are available from the Jexactyl panel.

What is code-server?

code-server brings VS Code to the browser: edit, integrated terminal, extensions — on a remote machine. Ideal to code from a Chromebook, troubleshoot a server, or standardize a dev environment.

On 1VPS, code-server is a one-click template. You authenticate access and clone your repos; we provide NVMe, IP and AS219084. Protect the UI (strong password, HTTPS, ideally VPN): it is an exposed IDE.

• Web VS Code with terminal and extensions
• Remote dev without a heavy local stack
• Workspace on fast NVMe
• Secure access from the first login

Your IDE, your machine

Extensions, runtimes (Node, Python…), Docker if co-installed: you build the environment the team needs.

Do not leave code-server open to the world without auth. Treat it as a development bastion.

• Auth + HTTPS mandatory in prod
• SSH keys for Git from the IDE
• Extensions aligned with your stack
• Snapshot before major upgrades

How do you get started with code-server?

Deploy, harden, then first repository.

1. 1. RAM for languages and builds — Simple editing: light plan. TypeScript/Java builds, containers: more RAM.
2. 2. Launch the code-server template — Software tab → code-server. Set the access password, note the URL.
3. 3. Domain, TLS, Git, workflow — DNS + HTTPS reverse-proxy, clone repos, configure Git, test the terminal. Disable anonymous access.

What is code-server for?

Remote dev, training, editing bastion.

It is not a CI replacement. It is a remote workstation.

• Nomad dev — Code from any browser on the same machine.
• Onboarding — A pre-tooled environment for a new teammate.
• Prod-like debug — Edit close to infra (with discipline and limited rights).
• Workshops — Sessions where everyone opens the same stack via URL.

How do I deploy code-server?

Pick the code-server egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize code-server?

Yes — files, variables and console are available from the Jexactyl panel.

What is Uptime Kuma?

Uptime Kuma is a self-hosted uptime monitor: HTTP(S), TCP, ping, DNS, TLS certificates, public status pages — with alerts (email, Telegram, Discord, webhooks…). You see when a service dies, without an opaque monitoring SaaS.

On 1VPS, Uptime Kuma is a light one-click template. Put it on a modest plan dedicated to monitoring (ideally not on the same machine as the critical service you watch). NVMe + AS219084 for the exposed UI.

• HTTP, ports, ping, keywords, certificate checks
• Multi-channel alerts
• Shareable status page
• Visible history and latency

How do you set up Uptime Kuma?

Deploy, add monitors, wire alerts.

1. 1. A small dedicated plan — Kuma is light. Give it a separate instance from critical prod to avoid the blind spot “everything is down including the monitor”.
2. 2. Launch the template — Software tab → Uptime Kuma. Create the admin account on first visit.
3. 3. Monitors, alerts, status page — Add your URLs/endpoints, configure notifications, publish a status page if needed, DNS + HTTPS. Snapshot after a stable config.

What is Uptime Kuma for?

Simple visibility into service availability.

It is not a full APM (traces, profiling). It is the excellent “does it answer?” safety net.

• Sites & APIs — HTTP 200, keywords, soon-expiring certificates.
• TCP infra — SSH, game ports, SMTP, Redis…
• Customer status — Public page during an incident.
• Team alerting — Discord/Telegram/email as soon as a check fails.

How do I deploy Uptime Kuma?

Pick the Uptime Kuma egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Uptime Kuma?

Yes — files, variables and console are available from the Jexactyl panel.

What is a TeamSpeak server?

TeamSpeak is a low-latency voice reference for gaming communities and teams. A TeamSpeak server hosts your channels, permissions and users — with stable audio quality when network and instance keep up.

On 1VPS, TeamSpeak is a one-click template on a fixed RAM plan, with AS219084 Anti-DDoS (critical for exposed voice). You administer privilege keys, channels and bots; we provide Brussels infra.

• Clear voice for clans, communities, staff
• Fine permissions per channel / group
• AS219084 mitigation on voice ports
• Size for concurrent slots

How do you open a TeamSpeak?

Deploy, privilege key, channel structure.

1. 1. Estimate slots — Small team: entry plan. Large communities / events: more RAM and watch fair-use bandwidth.
2. 2. Launch the TeamSpeak template — VoIP tab → TeamSpeak. Get privilege key / admin token per template, note IP and ports.
3. 3. Channels, rights, optional DNS — Create the channel tree, server groups, bans. Point a subdomain if needed. Snapshot after a stable config.

What is TeamSpeak for?

Structured, durable voice with a real channel tree.

For ephemeral friend voice, Discord is sometimes enough. TeamSpeak shines for communities that want to control the server.

• Clan / guild — Channels per game, staff, AFK — clear rights.
• Community — Events, support, voice announcements.
• Esports team — Scrim / match comms with low latency.
• Project staff — Pro voice for remote gaming-adjacent teams.

How is the TeamSpeak 3 offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the TeamSpeak 3 stack?

Yes. Versions and components (e.g. 3.13, query, webrtc) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is a Mumble server?

Mumble is an open-source voice server focused on latency and clarity: perfect for competitive gaming and teams that want a simple server without bloat. Less “social network” than Discord, more direct.

On 1VPS, Mumble is a one-click template. Low resource footprint, AS219084 Anti-DDoS on the ports. You manage channels and ACLs; official clients connect in a few clicks.

• Low latency, Opus codec
• Granular ACLs per channel
• Light on RAM vs richer stacks
• Certificate / auth depending on config

How do you deploy Mumble?

Instance, SuperUser password, channel tree.

1. 1. Entry plan often enough — Mumble is frugal. Raise the plan for very large slots or lots of voice bandwidth.
2. 2. Launch the Mumble template — VoIP tab → Mumble. Get the SuperUser password / panel info, note IP:port.
3. 3. Clients, ACLs, hardening — Connect the official client, create channels and groups, restrict root rights. Snapshot after config.

What is Mumble for?

Minimalist, high-performance voice.

If you want rich bots and social integrations, TeamSpeak/Discord may fit better. Mumble wins on simplicity and latency.

• Scrims — Clean comms for competitive teams.
• Lan party / event — Temporary or recurring server for an event.
• Overkill-free community — Just voice, no app marketplace.
• Voice backup — Fallback if Discord/TS is down.

How is the Mumble offer deployed?

The app is provisioned automatically (ready stack). Panel/files/DB access (depending on the offer) is available in dash.1vps.cc minutes after payment.

Can I customize the Mumble stack?

Yes. Versions and components (e.g. 1.5, 1.4, ice) are manageable; files, vhosts and databases stay accessible depending on the offer.

What is a Node.js VPS?

A Node.js runtime ready for APIs, Discord bots, workers, light SSR or long-running CLI tools. You deploy your JavaScript/TypeScript code without installing Node from repos every time.

On 1VPS, the Node.js template runs on a fixed RAM plan. Process manager, env vars and ports: yours. NVMe + AS219084 for exposed services. This is not serverless: a memory-leaking process stays down until you intervene.

• Node LTS ready for npm/pnpm/yarn
• Ideal bots, Express/Fastify APIs, scrapers
• Logs and restart via panel / PM2
• Size for heap and concurrency

The right level of control

Enough access to debug and deploy, without rebuilding the runtime on every instance.

Native builds (node-gyp) and huge bundles can exceed RAM — size and externalize if needed.

• Ready-to-use runtime
• Panel restart and logs
• RAM plan = real capacity
• Same panel as the rest of 1VPS cloud

How do you deploy a Node.js app?

Template → code → durable process.

1. 1. Estimate heap and traffic — Quiet bot: small plan. Public API or many websockets: more RAM. Leave GC headroom.
2. 2. Launch the Node.js template — Runtimes tab → Node.js. SSH/panel, clone the repo, `npm i`, configure `.env`.
3. 3. Process manager, reverse-proxy, watch — PM2/systemd, DNS + proxy, healthchecks. Snapshot before release; watch memory RSS.

What projects fit Node.js?

Server-side JavaScript, bots and APIs.

For a pure CMS site, prefer WordPress/Drupal. Node shines once you write application logic.

• Discord / Telegram bot — Gateway intents, shards for large communities.
• JSON API — REST/GraphQL for mobile or a decoupled front.
• Workers — Queues, cron, async jobs.
• Light SSR — Small React/Vue apps served in Node.

How do I deploy my app on Node.js?

The runtime environment is ready after provisioning. Push via Git, CLI or files, then manage processes/logs from dash.1vps.cc.

Which Node.js versions are supported?

Among others: 22, 20, 18. Pick the version at deploy time to match your stack.

What is a Python VPS?

A Python runtime ready for APIs (FastAPI/Django/Flask), bots, scrapers, light notebooks or data jobs. You bring venv/poetry and code; the instance skips “compile Python from source”.

On 1VPS, Python template on a fixed RAM plan, NVMe and AS219084. Scientific libs and light ML models eat RAM fast — be honest about the workload.

• Modern Python ready for venv/poetry
• APIs, bots, automation, light ETL
• Durable processes via systemd/supervisord
• Watch native deps (wheels)

Your Python stack

Choose the framework, Celery/RQ workers, remote or local DB. No PaaS forcing one deploy style.

Massive `pip` installs and native builds can saturate CPU/RAM during deploy — do it off-peak or on a larger plan.

• Isolated venvs per project
• Clear environment variables
• App logs + panel
• Snapshots before runtime upgrades

How do you deploy a Python app?

Template → venv → service.

1. 1. Size for libraries — Script / bot: small plan. Django + workers or heavy pandas: more RAM.
2. 2. Launch the Python template — Runtimes tab → Python. Create the venv, install `requirements.txt` / poetry.
3. 3. Service, proxy, observability — Gunicorn/Uvicorn + systemd, DNS/TLS, healthcheck. Backup code and related DB.

What projects fit Python?

APIs, automation and light data.

For GPU deep learning, this is not the offer. For APIs and bots: excellent simplicity / control ratio.

• FastAPI / Django API — JSON backend for front or mobile.
• Bots & automation — Discord, legitimate scraping, business cron.
• Light ETL — Periodic jobs, exports, syncs.
• Data prototypes — Notebooks / scripts on NVMe (no GPU).

How do I deploy my app on Python?

The runtime environment is ready after provisioning. Push via Git, CLI or files, then manage processes/logs from dash.1vps.cc.

Which Python versions are supported?

Among others: 3.13, 3.12, 3.11. Pick the version at deploy time to match your stack.

What is Minecraft hosting?

Minecraft hosting is a Java server (or Bedrock via another template) online 24/7 with a dedicated IP. Players join your world; you pick the engine (Paper, Spigot, Purpur, vanilla…), plugins, version and community rules.

At 1VPS, the Minecraft egg prepares the environment: console, restart, files and a fixed RAM plan. AS219084 Anti-DDoS protects the IP — useful once the server is public. Compute is in Brussels: latency follows real network distance, not an invented “gaming DC”.

• Ready egg: versions and engines per catalog
• Plan RAM = players + plugins / view-distance
• Worlds on NVMe; panel snapshots + world backups recommended
• AS219084 mitigation included, no surprise mitigation fee

How do you deploy your Minecraft server?

From order to the first player in survival — concrete steps, no useless jargon.

1. 1. Pick RAM for your game mode — Vanilla survival / light plugins: an entry plan can work. Minigames, heavy plugin packs or many players: raise RAM. A hungry Forge/Fabric modpack often needs far more than simple survival.
2. 2. Deploy the egg and choose version / engine — Select Minecraft in the games tab, confirm the plan, then the image. In ~1 minute the instance is ready. In the panel: pick Paper/Spigot/vanilla (per offer), the version, and open the console.
3. 3. Configure the world, then open to players — Edit server.properties (slots, difficulty, online-mode), add plugins via files, test on the IP. Then whitelist or public, optional DNS, and schedule world backups before big changes.

Which Minecraft projects fit?

From a friends server to a more ambitious network — the plan follows real load.

Minecraft is not “one slot = fixed RAM”: view-distance, redstone, plugins and loaded chunks weigh as much as the player counter.

• Survival / SMP — Persistent world, whitelist or semi-public, light economy. Ideal to start: few heavy plugins, controlled RAM, regular world backups.
• Minigames & lobbies — Frequent resets, multiple worlds, sometimes a separate proxy (Bungee/Velocity). Plan more RAM and clear instance layout.
• Forge / Fabric modpacks — Much hungrier than vanilla. Size large, cut unused mods, and expect longer boot restarts.
• Multi-server network — Proxy + several backends (lobby, survival, minigames). Each node has its plan; a whole network will not fit on 2 GB.

What keeps a Minecraft server healthy

Concrete levers before blaming only the host.

If TPS drops, check plugins, view-distance and entities — then upscale RAM if the diagnosis is clear.

• TPS & RAM — More chunks and plugins = more memory. Undersizing shows as immediate lag.
• World backups — Instance snapshots help, but a world-folder backup is safety before wipe or upgrade.
• Anti-DDoS — AS219084 on the game IP once public — raids are part of the landscape.
• Versions — Switch version / engine via the egg; test plugins before forcing a major upgrade.

How do I start a Minecraft Java server?

Pick the offer, confirm your RAM plan, and the instance is ready in minutes. Live console, files and restarts live in dash.1vps.cc.

Which engines / versions for Minecraft Java?

Notably available: paper, spigot, forge. More builds may appear at deploy time (+ extras depending on the offer).

What is FiveM hosting?

FiveM hosts modded GTA V servers: roleplay, freeroam, races, frameworks (ESX, QBCore…). FiveM hosting is the infra + template that keep FXServer online 24/7 with a dedicated IP, enough RAM for resources, and mitigation that can take raids.

At 1VPS: FiveM egg, console, panel restart, fixed RAM plan, AS219084 Anti-DDoS. You manage artifacts, resources and the Cfx.re key. Compute in Brussels — real latency, no invented gaming anycast.

• FiveM template and versions per catalog
• AS219084 included (attacks are common on RP)
• Readable RAM for slots + heavy resources
• Cfx.re license / key is yours — stated clearly

How do you deploy a FiveM server?

From plan to first player in the city — the concrete path, resource by resource.

1. 1. Size RAM for your server type — Light freeroam ≠ heavy ESX/QBCore RP with resources and OneSync. Poorly optimized maps and scripts eat memory. Aiming for a big RP city? Start large: day-one hitching kills players faster than a slightly higher price.
2. 2. Deploy the FiveM egg and set the base — Pick FiveM in games, deploy. In the panel: artifacts / build, server.cfg, Cfx.re key (yours), resources folders. Add the framework (ESX, QBCore…) then resources one by one — not everything at once.
3. 3. Test, open Discord, then scale load — Connect, check console errors, staff permissions and economy. Open to players gradually. If the server hitchs: remove resources, then upscale RAM if needed. Snapshots before big additions.

Which FiveM projects fit?

RP communities and public servers that need a stable IP.

A living FiveM server is as much Discord and staff as tech. Infra simply must not be the weak link.

• RP server — Economy, jobs, inventory, Discord staff — the classic that needs RAM and stability.
• Freeroam / fun — Lighter sessions, events, less framework — ideal to start and learn.
• Heavy resources — Ambitious maps and scripts: plan the forfait accordingly or hitch is guaranteed.
• OneSync & slots — More concurrent players = more network sync and RAM. We upscale instead of lying about slots.

FiveM essentials

What separates a playable server from one that lags.

Optimize resources before blaming only the host — then size up if the diagnosis is clear.

• RAM & slots — Undersizing produces immediate hitching, even on a good network.
• AS219084 Anti-DDoS — Mitigation on the FXServer IP — essential once the server is public.
• Artifacts — Keep the build current via egg / panel for client-server stability.
• Cfx license — The key remains your vendor responsibility — we do not hide it in the price.

How do I start a FiveM server?

Pick the offer, confirm your RAM plan, and the instance is ready in minutes. Live console, files and restarts live in dash.1vps.cc.

Which engines / versions for FiveM?

Notably available: txadmin, artifacts, onesync. More builds may appear at deploy time (+ extras depending on the offer).

What is Rust hosting?

Rust is hardcore survival: procedural map, raids, wipe schedule, often Oxide/uMod for plugins. Rust hosting is a machine strong enough to run the Facepunch dedicated server, with enough RAM and disk I/O for the map and saves — and an IP that survives network attacks.

At 1VPS, the Rust egg handles the base (console, restart, files). You configure wipe, map size, plugins and rates. Brussels compute, AS219084 Anti-DDoS included. Rust is hungry: undersize RAM and you get stutter, not cosmetic lag.

• Ready Rust egg: console, files, panel restart
• RAM plans suited to maps and Oxide plugins
• NVMe for saves / map — slow disks show immediately
• AS219084 Anti-DDoS on the public IP

How do you deploy a Rust server?

From plan to first wipe — what to do concretely.

1. 1. Size for map and plugins — A small map + few plugins ≠ a large map + heavy Oxide. Start larger for a public wipe; you can adjust later, but starting too small ruins wipe day one.
2. 2. Deploy the egg and configure — Pick Rust in games, deploy. In the panel: server settings (name, slots, map size), install Oxide/uMod if needed, add plugins, plan the wipe schedule.
3. 3. Test, open, then run the wipe cycle — Connect, check perf and plugins, then open to players. Before each wipe: backup useful data, Discord comms, clean restart. Snapshots help; a clear wipe process is still required.

Which Rust projects fit?

Community, modded or vanilla servers — with an assumed wipe rhythm.

Rust lives on wipe cycles. Hosting must follow: restarts, I/O, mitigation — not only “slots”.

• Vanilla / semi-vanilla — Few plugins, Facepunch gameplay focus. Easier to run, but map size still drives RAM.
• Oxide / uMod modded — Kits, teleports, custom rates… more fun, heavier. Plan RAM and test plugins before public wipe.
• Weekly / bi-weekly wipe — Regular community, announced calendar. Stable wipe process matters as much as config.
• Public exposed server — Listed and attacked: AS219084 on the IP is not a marketing bonus, it is the minimum.

Rust essentials

What avoids a wipe failure on day one.

Stutter often comes from a tight plan or bad plugins — before the network.

• RAM & map size — Larger, busier maps need more memory. Do not copy another server’s slots without reading the config.
• Saves & NVMe — Frequent saves love fast disk. Anemic storage shows up as freezes.
• Wipe cycle — Backup, announce, wipe, restart: a written process beats Discord improvisation.
• Anti-DDoS — AS219084 on the public IP — network raids are common on Rust.

How do I start a Rust server?

Pick the offer, confirm your RAM plan, and the instance is ready in minutes. Live console, files and restarts live in dash.1vps.cc.

Which engines / versions for Rust?

Notably available: oxide, carbon, vanilla. More builds may appear at deploy time (+ extras depending on the offer).

What is CS2 hosting?

Counter-Strike 2 dedicated hosting runs Valve’s game server for customs, scrims or community play. Unlike Minecraft or Rust, this is not about “modpacks”: it is tickrate, slots, competitive configs, optional plugins and a stable IP so players join without friction.

At 1VPS, the CS2 template provides console, restart and a RAM plan. AS219084 Anti-DDoS protects the IP — useful once a server is listed or known. Compute in Brussels; “network feel” also depends on player connections, not only the server.

• CS2 template: panel console and config files
• Plan sized for slots and target tickrate
• Dedicated IP + AS219084 Anti-DDoS included
• Valve licenses / requirements remain yours

How do you deploy a CS2 server?

From plan to first custom — concrete steps.

1. 1. Pick a plan for slots and usage — A 5v5 custom is not the same as a fuller community server. Leave headroom for plugins or heavy use; useful tickrate also depends on config and plan.
2. 2. Deploy the template and configure — Select CS2 in games, deploy. In the panel: server name, slots, config files (server.cfg / modes), maps. Test a local connection on the IP before inviting the team.
3. 3. Open to players and iterate on config — Share IP or DNS, tune cvars for scrim or fun. Watch stability; on lag reports, check config and load before blaming only the network.

Which CS2 projects fit?

Customs, scrims and community servers — not an RPG with mod packs.

CS2 lives on config and IP consistency. Hosting must be predictable; competitive feel also depends on clients.

• Customs & scrims — Organized matches, competitive configs, fewer players but high stability and fixed-IP expectations.
• Community server — Fun maps, optional plugins, regular hours. Size slots without over-promising.
• Team practice — Private server for a roster: controlled access, frozen configs, fast panel restarts.
• Exposed server — Known outside a private circle: AS219084 on the IP becomes a real criterion, not a marketing checkbox.

CS2 essentials

What actually matters for a playable server.

Network feel depends on the server and client connections. We stay honest about that.

• Slots & plan — More players and plugins = more load. Align the plan with real usage.
• Configs & modes — server.cfg, modes, maps: server quality is largely in the files.
• Stable IP — Teams bookmark an IP. Avoid hosts that move constantly.
• Anti-DDoS — AS219084 on the public IP for known or listed servers.

How do I start a Counter-Strike 2 server?

Pick the offer, confirm your RAM plan, and the instance is ready in minutes. Live console, files and restarts live in dash.1vps.cc.

Which engines / versions for Counter-Strike 2?

Notably available: vanilla, tick128, competitive. More builds may appear at deploy time (+ extras depending on the offer).

What is Azuriom?

Azuriom is a CMS built for gaming communities: server brochure site, news, rank shop, voting, docs and player auth. Where generic WordPress needs plugins everywhere, Azuriom already speaks “Minecraft / FiveM / Rust server”.

On 1VPS, Azuriom is a one-click template on a fixed RAM plan (web offer: sites*, SSL, DBs*). You stay theme/plugin admin; we provide Brussels NVMe, dedicated IPv4 and AS219084 Anti-DDoS. Ideal to pair a real site with your 1VPS game server.

• Gaming CMS: news, shop, votes, community pages
• SSL and unlimited DBs* on the RAM plan
• Easy to pair with a 1VPS-hosted game server
• You administer Azuriom plugins and content

How do you deploy Azuriom for real?

From plan to first admin login — no LEMP DIY.

1. 1. Size for the community — Small guild / chill server: Essential is often enough. Active shop, many plugins or vote spikes: start on Pro. Unlimited if you stack heavy site traffic + game APIs.
2. 2. Launch the Azuriom template — Web tab → Azuriom → confirm. In ~60s the stack is ready. Grab admin URL and IP in dash.1vps.cc.
3. 3. Domain, SSL, game-server link — DNS A to the IPv4, enable HTTPS, configure shop/votes, wire auth or server plugin. Snapshot before every big plugin.

What projects fit Azuriom?

Any site that lives around a game server.

Azuriom is not a generic corporate CMS: it shines when the community and the server are the product.

• Minecraft site — News, votes, rank shop, rules and light wiki.
• FiveM / GTA RP — Whitelist, vehicle shop, staff announcements.
• Rust / survival server — Kits, VIP, wipe calendar.
• Multi-game network — Community hub + links to several 1VPS servers.

How do I deploy Azuriom?

Pick the Azuriom egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Azuriom?

Yes — files, variables and console are available from the Jexactyl panel.

What is an FFmpeg VPS?

FFmpeg is the audio/video encoding toolkit: convert, cut, transcode, generate thumbnails, prepare streams for Jellyfin or a batch pipeline. An FFmpeg VPS gives you a dedicated machine with binaries ready — no toolchain install on every job.

On 1VPS, the FFmpeg template runs on a fixed RAM plan and NVMe. This is not a managed encoding SaaS: you run commands/scripts. Size CPU/RAM for resolution and parallelism — heavy transcode loves headroom.

• FFmpeg / ffprobe ready in ~60s
• NVMe for media I/O, AS219084 Anti-DDoS on the IP
• Ideal for batch, cron, or Jellyfin complement
• You steer scripts, queues and storage

How do you use FFmpeg on 1VPS?

From plan to first successful encode.

1. 1. Pick for the encodes — Small 720p batches: Essential. Regular 1080p multi-stream: Pro. 4K / many parallel jobs: Unlimited (CPU will be the bottleneck).
2. 2. Deploy the template — Web tab → FFmpeg. Check `ffmpeg -version` in console. Mount media (SFTP, rsync, volume).
3. 3. Automate carefully — Scripts, cron, queues. Snapshot before binary upgrades. Watch disk: encode temps grow fast.

What projects fit FFmpeg?

Any pipeline that transforms media.

Respect fair-use and the rights of content you encode.

• VOD batch — Convert a library to H.264/H.265 for archive.
• Jellyfin complement — Pre-transcode heavy titles off-peak.
• Media CI pipelines — Post-upload jobs (thumbs, HLS segments).
• Podcast / audio — Normalize, split, multi-format exports.

How do I deploy FFmpeg?

Pick the FFmpeg egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize FFmpeg?

Yes — files, variables and console are available from the Jexactyl panel.

What is Panelactyl?

Panelactyl (often tied to the Pterodactyl ecosystem) provides an admin UI to drive game nodes and servers. It is the “panel” layer: accounts, allocations, eggs — not the Minecraft server itself.

On 1VPS, the template gets you the UI quickly on a RAM plan. You must harden HTTPS, admin auth and the link to your nodes (Wings). Not managed game hosting: your cockpit.

• Self-host games admin UI
• HTTPS and allowlist strongly recommended
• Pair with 1VPS game nodes / servers
• Snapshot panel config before upgrades

You orchestrate the farm

Users, servers, allocations: the Pterodactyl model stays yours. 1VPS provides the panel instance, not team policy.

An exposed panel without hardening is a target: MFA, IP allowlist, strong passwords, panel DB backups.

• Split panel and nodes when possible
• Do not publish admin to the whole internet
• Document eggs and allocations
• Test snapshot restore off prod

How do you deploy Panelactyl?

Panel first, nodes second.

1. 1. Plan by farm size — 1 node / few users: Essential. Multi-node: Pro. Large network: Unlimited.
2. 2. Template + HTTPS — Deploy, point domain, force HTTPS, change all default secrets.
3. 3. Wire Wings / servers — Add nodes, create a test server, snapshot panel once stable.

What is it for?

Centralized game-server admin.

If you just want Minecraft without a panel, use 1VPS game servers instead.

• Minecraft network — Lobby + survival + minigames via eggs.
• Agency / reseller — Isolated clients under one panel.
• Community — Staff with granular permissions.
• Eggs lab — Test images and allocations.

How do I deploy PanelDactyl?

Pick the PanelDactyl egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize PanelDactyl?

Yes — files, variables and console are available from the Jexactyl panel.

What is RethinkDB?

RethinkDB is a realtime-oriented NoSQL database: changefeed queries push updates to clients. Useful for live dashboards, collab, or backends that react to inserts without polling.

On 1VPS, the template starts a node quickly. You harden the admin UI, auth and network bind. Not a managed multi-AZ cluster: size and replicate per your design.

• Realtime changefeeds
• Harden admin UI immediately
• Firewall: no public listen by default
• Snapshots before migrations / upgrades

Control listen and feeds

Tables, secondary indexes, permissions: you model. Keep the UI off the internet or behind VPN.

Changefeeds cost CPU/RAM with fan-out — overload and the DB will tell you.

• Bind localhost / private IP
• Admin allowlist
• Only useful indexes
• Logical backup + snapshot

How do you deploy RethinkDB?

From template to first changefeed.

1. 1. Plan by fan-out — Proto: Essential. Light prod: Pro. Many feeds: Unlimited.
2. 2. Template + lockdown — Deploy, change admin access, close public ports.
3. 3. App + snapshot — Wire your client, test a feed, baseline snapshot.

What projects fit?

Live backends and light collab.

For classic SQL, prefer PostgreSQL / MariaDB.

• Live dashboard — Pushed metrics without refresh.
• Doc collab — Presence / approximate cursors.
• Light IoT — Modest realtime events.
• API prototype — Validate a push model before Kafka.

How do I deploy RethinkDB?

Pick the RethinkDB egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize RethinkDB?

Yes — files, variables and console are available from the Jexactyl panel.

What is Lavalink?

Lavalink is an audio node used by Discord bots (and similar ecosystems): the bot offloads streaming/encoding to Lavalink instead of doing everything in the bot process.

On 1VPS, the template starts the service quickly. You configure password, ports, and the connection from your bots. Size by guild count / concurrent streams.

• Dedicated audio node for bots
• Open ports toward your bots only
• Logs / process visible in console
• Snapshot YAML/password config

Your audio, your bots

Several bots can point at the same node (within RAM/CPU limits). You manage password and firewall.

Do not expose Lavalink to the whole internet without strong auth — it is attractive CPU.

• Long password + rotate if leaked
• Bot IP allowlist
• Watch CPU load
• Split prod / lab

How do you deploy Lavalink?

Service first, bots second.

1. 1. Plan by streams — 1–2 bots: Essential. Several active guilds: Pro. Heavy audio concurrency: Unlimited.
2. 2. Template + password — Deploy, change the secret, note host:port.
3. 3. Wire bots — Bot config → Lavalink, test a play, snapshot config.

What is it for?

Discord music / audio bots.

Respect Discord ToS and music rights.

• Community music bot — Playlists for one server.
• Multi-bots — Several bots → one node.
• Codecs lab — Test load and quality.
• Backup node — Secondary Lavalink failover.

How do I deploy Lavalink?

Pick the Lavalink egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Lavalink?

Yes — files, variables and console are available from the Jexactyl panel.

What is TS3 Manager?

TS3 Manager is an administration UI for TeamSpeak servers: manage instances, permissions and day-to-day ops via web UI rather than only the client / ServerQuery.

On 1VPS, the template deploys the UI. You must put it on HTTPS, restrict access, and point it at your TeamSpeak instances (ideally also on 1VPS).

• TeamSpeak admin UI
• HTTPS + allowlist recommended
• Complements the TeamSpeak template
• Snapshots before UI upgrades

Frictionless voice admin

Delegate staff rights via the UI while keeping privilege keys under control.

An exposed admin UI is an attack surface: treat it like a bastion.

• Named admin accounts
• No cleartext HTTP UI
• Log sensitive actions
• Backup manager config

How do you deploy TS3 Manager?

Secure UI, then link TS.

1. 1. Light plan often OK — Essential for 1 TS instance. Pro for multi-server / heavy ops.
2. 2. Template + HTTPS — Deploy, domain, cert, fresh secrets.
3. 3. Connect TeamSpeak — Add the TS instance, test an admin action, snapshot.

What is it for?

Day-to-day TeamSpeak ops.

For voice itself, also deploy the TeamSpeak template.

• Gaming community — Multi-level staff.
• Clan / org — Centralized rooms and tokens.
• Multi-instance — Several TS behind one UI.
• Delegation — Mods without raw ServerQuery.

How do I deploy TS3 Manager?

Pick the TS3 Manager egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize TS3 Manager?

Yes — files, variables and console are available from the Jexactyl panel.

What is Elasticsearch?

Elasticsearch is a search / analytics engine: document indexing, full-text queries, aggregations. Often used for logs (ELK), product search, or light analytics.

On 1VPS, the template starts a single-node instance. You must fit the JVM heap into plan RAM, close the API to the public, and plan index snapshots. Not managed Elastic Cloud.

• Search & aggregations
• JVM heap ≤ ~50% of plan RAM
• API not exposed without auth / firewall
• Index snapshots before reindex

You steer indexes and retention

Mappings, DIY ILM, aliases: yours. Watch NVMe disk — shards grow fast.

An open Elasticsearch without auth was the internet’s nightmare in the 2010s. Do not repeat it.

• Security / auth enabled
• Private bind
• Bounded log retention
• ES snapshot backups + disk

How do you deploy Elasticsearch?

Heap, security, then data.

1. 1. RAM first — Dev: Essential. Single-node prod: Pro minimum. Large indexes: Unlimited and accept single-node limits.
2. 2. Template + harden — Deploy, enable auth, close 9200 to the public.
3. 3. Index + snapshot — Create a test index, wire Filebeat/app, policy snapshot.

What projects fit?

App search and logs.

For relational SQL, stay on Postgres/MariaDB.

• Product search — Catalog / full-text docs.
• App logs — Light ELK-style centralization.
• Analytics — Dashboard aggregations.
• Mapping lab — Test analyzers before prod.

How do I deploy Elasticsearch?

Pick the Elasticsearch egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Elasticsearch?

Yes — files, variables and console are available from the Jexactyl panel.

What is Forgejo?

Forgejo is a community Git forge (Gitea fork): repos, issues, PRs, packages and light CI actions — self-hosted, no SaaS dependency. You keep code and metadata on your instance.

On 1VPS, Forgejo is a one-click template on a RAM plan. You admin users, orgs and runners; we provide NVMe, IPv4 and AS219084. Lighter than full GitLab, more “forge” than bare Git.

• Git HTTPS/SSH + modern web UI
• Issues, PRs, packages per your config
• Actions / CI possible depending on resources
• Snapshots before major forge upgrades

Your forge, your rules

Orgs, team permissions, mirrors, webhooks: you define the workflow. No artificial “SaaS plan” limits.

A forge only helps if access is clean: user SSO/MFA, SSH keys, and repo backups (not only disk snapshots).

• Private / public repos as you choose
• Webhooks to external CI if needed
• Firewall: open only useful 22/443
• Export / mirror before migration

How do you deploy Forgejo?

From plan to first `git push`.

1. 1. RAM by team and CI — Solo / small team: Essential. Several orgs + Actions: Pro. Large mirrors / heavy CI: Unlimited.
2. 2. Forgejo template — Software tab → Forgejo. Create admin, note URL, enable HTTPS on your domain.
3. 3. Users, SSH, first repo — Add accounts, upload SSH keys, create a test repo, baseline snapshot.

What projects fit Forgejo?

Private code, team forge, light GitHub/GitLab SaaS alternative.

For a monstrous GitLab-style runner farm, size differently (or talk to us).

• Product team — Private repos, PRs, reviews.
• Indie / OSS — Light public forge under your domain.
• Internal mirror — Copy of critical repos, on-prem style.
• DevOps lab — Test Actions / webhooks without SaaS.

How do I deploy Forgejo?

Pick the Forgejo egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Forgejo?

Yes — files, variables and console are available from the Jexactyl panel.

What is Hastebin?

Hastebin is a self-host paste service: quickly share snippets, logs, configs — under your domain, without a third-party public paste.

On 1VPS, the template is light. Even for a small app: HTTPS, rate-limits and retention policy remain yours.

• Private / team paste under your domain
• HTTPS recommended from day one
• Low RAM footprint
• Snapshot paste storage

Your paste, your rules

Public, auth, paste TTL: you decide. Useful internally to share logs without a SaaS.

A public paste without moderation attracts spam — plan auth or a private network.

• Auth if internet-facing
• Purge / retention
• Reverse proxy + security headers
• Backup data dir

How do you deploy Hastebin?

Template, domain, harden.

1. 1. Essential is often enough — Raise the plan only for large paste volume.
2. 2. Deploy + HTTPS — Software tab → Hastebin, DNS, cert.
3. 3. Access policy — Auth / VPN / allowlist, then snapshot.

What is it for?

Controlled short-text sharing.

Not a Drive and not Git.

• Support logs — Paste a traceback for staff.
• Temp configs — Exchange a snippet outside chat.
• Internal team — Paste behind VPN.
• Workshop demo — Quick share in training.

How do I deploy Hastebin?

Pick the Hastebin egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Hastebin?

Yes — files, variables and console are available from the Jexactyl panel.

What is Prometheus?

Prometheus collects time-series metrics via HTTP scrapes: CPU, instrumented apps, exporters. Foundation of cloud-native monitoring, often paired with Grafana.

On 1VPS, the template starts Prometheus. You define targets, retention, and lock down the UI/API. Retention eats NVMe — bound it.

• Scrapes + alerting rules
• Disk retention to size
• UI/API not public without auth
• TSDB snapshots before upgrades

Your targets, your alerts

Scrape jobs, relabel, external Alertmanager: you compose. 1VPS does not “monitor for you”: we host the engine.

Too many high-frequency targets = explosive cardinality. Start small.

• Node / app exporters
• Realistic retention (days, not “infinite”)
• Auth proxy in front of the UI
• Backup rules YAML

How do you deploy Prometheus?

Engine, then targets.

1. 1. Plan by retention — Few hosts: Essential. App stack: Pro. Large scrape: Unlimited.
2. 2. Template + config — Deploy, edit prometheus.yml, add a test target.
3. 3. Harden + alert — Lock UI, wire Alertmanager/Grafana, snapshot.

What projects fit?

Self-host observability.

Pair with Grafana / Alertmanager as needed.

• VPS infra — Node exporter on your instances.
• Instrumented apps — HTTP / job metrics.
• Light SLOs — Availability / latency alerts.
• PromQL lab — Learn queries.

How do I deploy Prometheus?

Pick the Prometheus egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize Prometheus?

Yes — files, variables and console are available from the Jexactyl panel.

What is RabbitMQ?

RabbitMQ is an AMQP message broker: queues, exchanges, consumers. It decouples producers and workers (email jobs, webhooks, pipelines).

On 1VPS, the template starts the broker. You create users/vhosts, open ports sparingly, and watch queues that pile up.

• AMQP + management UI
• Isolated users / vhosts
• Firewall ports 5672/15672
• Export definitions + snapshots

Your queues, your consumers

Routing keys, DLQ, prefetch: your patterns. The broker does not forgive a broken consumer — messages pile up.

Exposed management UI = risk. Strong auth or VPN.

• One vhost per app
• Least-privilege permissions
• Alerts on queue depth
• Backup definitions.json

How do you deploy RabbitMQ?

Broker, users, then apps.

1. 1. Plan by throughput — Dev: Essential. App prod: Pro. Heavy traffic: Unlimited.
2. 2. Template + users — Deploy, create user/vhost, remove guest if exposed.
3. 3. Apps + harden — Wire producers/consumers, lock UI, snapshot.

What projects fit?

Async jobs and decoupling.

For massive Kafka-style pub/sub, different design.

• Emails / notifs — Workers off the HTTP request.
• Webhooks — Buffer queue to slow APIs.
• Light ETL pipelines — Decoupled stages.
• Microservices — Events between services.

How do I deploy RabbitMQ?

Pick the RabbitMQ egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize RabbitMQ?

Yes — files, variables and console are available from the Jexactyl panel.

What is a Java runtime on 1VPS?

The Java template provides an instance ready to run JVM apps (Spring Boot, Quarkus, custom jars) on a fixed RAM plan. You bring the artifact and config; we provide OS, base runtime, NVMe and Anti-DDoS.

Not a PaaS that builds for you: CI, optional Dockerfile, `-Xmx` heap and reverse proxy stay yours. Plan RAM must cover heap + OS + headroom.

• JVM ready — you deploy the jar/war
• Heap sized by Essential / Pro / Unlimited
• Console & process via panel/SSH
• Snapshots before artifact swap

Your JVM, your flags

GC, Spring profiles, env vars: free. No app vendor lock-in.

Frequent OOMs = plan too small or a leak — measure before blaming infra.

• systemd / process manager of choice
• Structured logs recommended
• HTTPS via Nginx/Caddy
• Application healthchecks

How do you deploy a Java app?

Runtime → artifact → proxy.

1. 1. RAM = heap + headroom — Light API: Essential. Business app: Pro. Large heap: Unlimited. Keep ~40–50% outside the heap.
2. 2. Java template — Deploy, upload the jar, configure the start service.
3. 3. Proxy + observability — HTTPS reverse proxy, logs, snapshot before prod.

What Java projects fit?

JVM APIs and services.

For pure Node frontends, prefer the Node/Next template.

• Spring Boot API — Business REST services.
• Batch workers — Scheduled JVM jobs.
• Connectors — Bridges to DBs/queues.
• Framework lab — Try Quarkus/Micronaut.

How do I deploy my app on Java?

The runtime environment is ready after provisioning. Push via Git, CLI or files, then manage processes/logs from dash.1vps.cc.

Which Java versions are supported?

Among others: 21, 17, 11. Pick the version at deploy time to match your stack.

What is a Go runtime on 1VPS?

The Go template prepares an instance to host compiled Go services: APIs, workers, proxies. You deploy the binary (or build on-box); RAM/NVMe/Anti-DDoS infra is provided.

Go loves small footprints — an entry plan often works. You keep the systemd unit, ports and reverse proxy.

• Ideal for binary APIs and microservices
• Low RAM vs typical JVM
• Firewall on the listener only
• Snapshot before binary swap

Single binary, simple ops

One file, flags, a unit — predictable deploys. No magic runtime.

Think healthchecks and graceful shutdown: clean SIGTERM.

• CI build → versioned artifact
• Env via files / systemd
• HTTPS terminated at the proxy
• Metrics / pprof if needed

How do you deploy a Go service?

Template → binary → ports.

1. 1. Plan by QPS — Light API: Essential. Multiple microservices: Pro. High QPS: Unlimited.
2. 2. Drop the binary — scp/CI to /opt/app, systemd unit, journald logs.
3. 3. Proxy + snapshot — Nginx → service, HTTPS, baseline snapshot.

What Go projects fit?

Fast services and workers.

For PHP/CMS, stay on web templates.

• JSON API — Lean handlers, low latency.
• Queue workers — Rabbit/Redis consumers.
• Proxies / sidecars — Small network services.
• Scheduled CLI — Cron’d binaries.

How do I deploy my app on Go?

The runtime environment is ready after provisioning. Push via Git, CLI or files, then manage processes/logs from dash.1vps.cc.

Which Go versions are supported?

Among others: 1.23, 1.22, 1.21. Pick the version at deploy time to match your stack.

What is a .NET / C# runtime on 1VPS?

The C# / .NET template prepares the instance to host ASP.NET apps (API, MVC, minimal APIs) on a RAM plan. You publish the app (`dotnet publish`); Kestrel listens locally, the reverse proxy terminates HTTPS.

Not Azure App Service: no managed build or magic slots. You keep appsettings, secrets and process. Ideal to leave opaque shared Windows/IIS.

• ASP.NET on 1VPS Linux
• Kestrel + Nginx/Caddy
• Secrets out of the repo
• Snapshots before publish

Your appsettings, your deps

Framework-dependent or self-contained: your call. Connection strings and DIY KeyVault-like stay yours.

Watch memory: .NET GC + concurrency can surprise on Essential.

• Development/Production environments
• Health endpoints
• Stdout → journald
• Separate DB migrations

How do you deploy a .NET app?

Publish → service → proxy.

1. 1. Plan by load — Light API: Essential. Business app: Pro. Heavy load: Unlimited.
2. 2. Publish to the instance — CI scp/rsync publish output, systemd unit `dotnet MyApp.dll`.
3. 3. HTTPS + snapshot — Reverse proxy, certificates, snapshot before opening traffic.

What .NET projects fit?

C# APIs and web apps.

For PHP CMS, stay on WordPress/Presta/LEMP.

• ASP.NET API — JSON business services.
• Internal MVC — Back-office tools.
• .NET workers — BackgroundService / queues.
• IIS migration — Leave shared Windows hosting.

How do I deploy C#?

Pick the C# egg in the catalog, confirm your RAM plan — the instance is ready in minutes on dash.1vps.cc.

Can I customize C#?

Yes — files, variables and console are available from the Jexactyl panel.