Cloud VPS Belgium — RAM plans from €5

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.

At 1VPS, the Debian instance runs in Brussels (compute), with Peeryx Anti-DDoS on the IP and network PoPs in Paris and Marseille. The public Looking Glass (Brussels probe) lets you measure real latency — no invented multi-datacenter marketing.

• Root SSH, HTML5 console and snapshots from dash.1vps.cc
• Fixed RAM plan: the capacity shown is what you get
• Dedicated IPv4 + Peeryx 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
• Peeryx 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.

Why choose our Debian VPS?

Because you want predictable root Linux: listed RAM plan, NVMe, IPv4, Peeryx Anti-DDoS, panel (console, snapshots, firewall), human support — without invented multi-datacenter storytelling.

Compute in Brussels, Peeryx PoPs in Paris and Marseille, public Looking Glass. We also say what stays yours (OS tuning, app dumps): that is an honest offer.

• Clear flat pricing — No opaque “usage” bill. Documented bandwidth fair-use.
• Network and mitigation included — Peeryx on the IP; FR PoPs to bring European traffic closer.
• Support on infra — Concrete help on the instance and network; app craft stays yours.

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.

At 1VPS, the Ubuntu instance runs in Brussels (compute), with Peeryx Anti-DDoS on the IP and network PoPs in Paris and Marseille. The public Looking Glass (Brussels probe) lets you measure real latency — no invented multi-datacenter marketing.

• Root SSH, HTML5 console and snapshots from dash.1vps.cc
• Fixed RAM plan: the capacity shown is what you get
• Dedicated IPv4 + Peeryx 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
• Peeryx 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.

Why choose our Ubuntu VPS?

Because you want predictable root Linux: listed RAM plan, NVMe, IPv4, Peeryx Anti-DDoS, panel (console, snapshots, firewall), human support — without invented multi-datacenter storytelling.

Compute in Brussels, Peeryx PoPs in Paris and Marseille, public Looking Glass. We also say what stays yours (OS tuning, app dumps): that is an honest offer.

• Clear flat pricing — No opaque “usage” bill. Documented bandwidth fair-use.
• Network and mitigation included — Peeryx on the IP; FR PoPs to bring European traffic closer.
• Support on infra — Concrete help on the instance and network; app craft stays yours.

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 Peeryx 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 Peeryx 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), Peeryx network 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.

Windows VPS: why 1VPS?

Belgian infra, Peeryx, clear plan, human support. We over-promise neither licensing nor invented multi-DC.

Need sizing help? Contact support before order — especially for heavy ERP.

• License transparency — We clarify the Windows model per offer instead of burying the topic.
• Anti-DDoS included — Peeryx on the IP even for exposed RDP use.
• Infra support — Help on the instance and network; Windows app config on your side.

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.

At 1VPS, the Docker template gives a ready environment for Compose, Hub images and multi-service stacks — with root/panel access, NVMe and Peeryx Anti-DDoS. One node = one plan: this is not managed Kubernetes. Brussels compute, Peeryx PoPs in France.

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

Orchestrate containers freely

Compose, light Swarm or Portainer — your choice. Private registries, multi-services, env vars — security remains yours.

Huge images and local builds consume plan CPU/RAM. Size correctly; do not expect magical horizontal auto-scale on one VPS.

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

How do you deploy Docker in practice?

From template to first `docker compose up` — what you actually do.

1. 1. Take a plan with RAM headroom — Images + active containers + local builds eat memory fast. For multi-service Compose (API, DB, reverse-proxy), do not start on the smallest plan “just to see”.
2. 2. Deploy the Docker template — In systems / templates, launch Docker. Once ready, connect (SSH or console). Check `docker` / `docker compose`, then stand up your stack (Compose files, networks, NVMe volumes).
3. 3. Expose cleanly, then iterate — Open only needed ports (firewall), add a reverse-proxy if required, keep secrets out of the repo. Snapshot before a risky image pull. If RAM saturates: upscale the plan instead of stacking more services.

Which Docker projects fit?

Whenever you want the same stack locally and in production, without “works on my machine”.

Docker shines at isolating services. For a multi-node cluster, talk architecture with us — a single VPS has honest limits.

• Microservices — Multiple Compose services (API, worker, cache, reverse-proxy) on one well-sized node.
• CI / runners — Containerized agents and jobs close to the code, with enough RAM for builds.
• Cloud-native apps — APIs + workers + cache in versioned containers; cloneable staging.
• Labs & staging — Clean disposable environments to validate a release before prod.

Why choose our Docker VPS?

Because you want Docker without rebuilding the daemon from scratch, while keeping root and honest resources. Guaranteed RAM plan, NVMe, Peeryx, 1VPS panel — not a ghost Kubernetes cluster sold as “magic”.

One node = one plan: we say so. Ideal to start Compose in light prod or staging, then raise RAM. Brussels infra, Peeryx PoPs, public Looking Glass.

• Ready environment, freedom after — Usable Docker template immediately, then Compose / Portainer / CLI like real prod.
• Honest resources — What the plan lists is what your containers can consume — no opaque auto-scale.
• Protected network — Peeryx Anti-DDoS as soon as you expose public ports.

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 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.

At 1VPS, WordPress is a one-click template on a fixed RAM plan, with NVMe storage and Peeryx Anti-DDoS. You remain the admin (plugins, themes, updates, cache): we speed up the start, we do not claim magical managed hosting. Compute in Brussels; Peeryx network PoPs in Paris and Marseille.

• WordPress ready in about 60 seconds after order
• Files / database access per offer, panel snapshots before risky upgrades
• Dedicated IP, readable RAM plan — ideal once shared hosting saturates
• Peeryx mitigation included; documented bandwidth fair-use

How do you deploy WordPress step by step?

The real path 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 builder, many extensions or traffic: take more RAM from the start. Better one step 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, database per offer) is ready. You get admin URL, panel access and details in dash.1vps.cc (and by email).
3. 3. Domain, content, then harden — Point your domain (DNS A to the IP), log into wp-admin, install only essential theme/plugins. Enable SSL per template, take a first snapshot before big changes, and plan app backups (not only disk snapshots).

Which WordPress projects fit?

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

WordPress stays versatile — you still size the plan for reality (cache, images, extensions). These are the most common uses among our customers.

• 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 shop: catalog, cart, payments. Plan more RAM and a cache strategy from day one.
• Multisite / agency — Multiple sites or client staging on the same plan logic — without opaque shared hosting.

Why choose our WordPress hosting?

Because you get one-click WordPress on clear infra: listed RAM plan, NVMe, dedicated IP, Peeryx Anti-DDoS included, human support. Not opaque shared hosting where you discover limits later.

You remain admin (updates, plugins, cache) — we say so. In return you keep control and measurable infra in Brussels, with Peeryx PoPs in Paris and Marseille. Public Looking Glass to test latency before migrating.

• Fast start, readable resources — Template ready in ~60 s, plus RAM and IP you understand — not a fuzzy “unlimited” offer.
• Protection and network included — Peeryx Anti-DDoS on the instance; FR PoPs for European traffic, without inventing multi-city compute.
• Migration help — Coming from elsewhere? We can help switch. Sizing and DNS: concrete answers.

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?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick Nextcloud in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit Nextcloud?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

Nextcloud hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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 GitLab VPS hosting?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick GitLab VPS in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit GitLab VPS?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

GitLab VPS hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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 Nginx + PHP hosting?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick Nginx + PHP in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit Nginx + PHP?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

Nginx + PHP hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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 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. Peeryx 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
• Peeryx 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 — Peeryx 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.

Why choose our Minecraft hosting?

Because we size honestly: current eggs, clear RAM plans, Peeryx Anti-DDoS included, simple panel for console and files. We do not promise 100 players on a tiny plan.

Infra in Brussels, measurable (Looking Glass). Human support for egg / network deploy; plugin vs performance balance remains your server craft — we help you not start on the wrong plan size.

• Eggs and versions kept current — Paper, Spigot, vanilla… per catalog, without dumping you on a bare OS on launch day.
• Mitigation included — Peeryx on the IP: useful as soon as the server leaves the friends circle.
• Sizing advice — We would rather say “take more RAM” than sell a plan that is too small.

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, Peeryx 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
• Peeryx 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.
• Peeryx 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.

Why choose our FiveM hosting?

Because RP lives or dies on stability and mitigation. We provide a clear FiveM egg, honest RAM plans for heavy resources, Peeryx Anti-DDoS included, and a panel for console / files / restart — without inventing twenty “gaming DCs”.

The Cfx.re key stays yours (we do not hide it in the price). Infra in Brussels, Looking Glass for latency. Support for egg deploy and network; resource scripting stays community-side.

• Built for real RP — We accept a heavy framework + maps costs RAM. Plans follow, without fantasy slots.
• Anti-DDoS without surprise — Peeryx included — raids are part of public FiveM life.
• Egg + grounded support — Deploy and network assisted; not a blank VPS with “figure it out”.

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, Peeryx 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
• Peeryx 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: Peeryx 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 — Peeryx on the public IP — network raids are common on Rust.

Why choose our Rust hosting?

Because Rust immediately punishes bad sizing. We offer honest RAM plans, a clear egg, NVMe, and Peeryx included — without promising miracles on a tiny plan.

Human support for deploy and network. Oxide plugins and wipe game design stay yours; we make sure infra is not the weak link.

• Plans for a heavy game — We accept Rust eats RAM; plans follow, without fantasy slot marketing.
• Peeryx mitigation — Included on the IP — useful as soon as a server goes public.
• Simple egg + panel — Console, files, restart without friction for wipe cycles.

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. Peeryx 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 + Peeryx 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: Peeryx 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 — Peeryx on the public IP for known or listed servers.

Why choose our CS2 hosting?

Because we treat CS2 as a competitive / community game server — not a generic VPS with a slogan. Clear template, readable plan, Peeryx included, panel for config and restart.

Infra in Brussels, Looking Glass for latency. We do not invent a magical “gaming PoP”: we give a stable base for your customs and scrims.

• Game template, not DIY from scratch — Console, files and restart without installing everything on a blank OS.
• Protected network — Peeryx Anti-DDoS once the server is exposed.
• Realistic promises — No fake marketing tickrate: we align plan, config and usage.

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 MariaDB hosting?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick MariaDB in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit MariaDB?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

MariaDB hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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 PostgreSQL hosting?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick PostgreSQL in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit PostgreSQL?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

PostgreSQL hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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 Redis hosting?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick Redis in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit Redis?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

Redis hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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 TeamSpeak 3 hosting?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick TeamSpeak 3 in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit TeamSpeak 3?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

TeamSpeak 3 hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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 Node.js runtime?

A ready template to run your Node.js apps: preinstalled runtime, environment variables, panel restart. Less friction than a bare VPS, without Kubernetes cluster complexity.

Capacity follows your RAM plan — not an opaque auto-scale PaaS. Secrets, deps and release hygiene stay yours. Infra in Brussels, Peeryx Anti-DDoS, network PoPs in France.

• Template runtime and process manager
• Env vars, restart and logs from the panel
• Snapshots before a risky release
• NVMe + Peeryx on network exposure

The right level of control

Enough access to debug and deploy, without installing the runtime from scratch every time.

Heavy native builds can exceed plan RAM — size accordingly.

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

Ship code, not the whole infra

The base is ready; you bring the application.

1. Pick the runtime — Select Node.js and a RAM plan that fits build + process in prod.
2. Push your app — Git / files depending on the template, configure environment variables.
3. Observe & iterate — Panel restart, logs, snapshots. Upgrade the plan if CPU/RAM saturate.

Which projects fit Node.js?

APIs, bots and side projects that must run 24/7 without heavy ops.

If you need horizontal auto-scale or a cluster, talk multi-node instead — support can help scope it.

• HTTP APIs — REST services, webhooks and light backends on a dedicated IP.
• Bots & workers — Discord, queues, long crons — processes that must survive restarts.
• Light SSR — Server-rendered frontends without standing up a full cluster.
• Staging — Cheaper prod mirrors to validate before release.

Node.js runtime: why 1VPS?

You see RAM, IP and Anti-DDoS. Flat pricing, unified panel, human support — no PaaS black box.

Same network promise as the cloud: Brussels + Peeryx PoPs, public Looking Glass.

• Readable capacity — The plan tells the truth about what the process can consume.
• One panel — Same experience as WordPress, Docker or Linux VPS.
• Simple upgrades — When traffic grows, upscale the plan instead of rebuilding everything.

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 runtime?

A ready template to run your Python apps: preinstalled runtime, environment variables, panel restart. Less friction than a bare VPS, without Kubernetes cluster complexity.

Capacity follows your RAM plan — not an opaque auto-scale PaaS. Secrets, deps and release hygiene stay yours. Infra in Brussels, Peeryx Anti-DDoS, network PoPs in France.

• Template runtime and process manager
• Env vars, restart and logs from the panel
• Snapshots before a risky release
• NVMe + Peeryx on network exposure

The right level of control

Enough access to debug and deploy, without installing the runtime from scratch every time.

Heavy native builds can exceed plan RAM — size accordingly.

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

Ship code, not the whole infra

The base is ready; you bring the application.

1. Pick the runtime — Select Python and a RAM plan that fits build + process in prod.
2. Push your app — Git / files depending on the template, configure environment variables.
3. Observe & iterate — Panel restart, logs, snapshots. Upgrade the plan if CPU/RAM saturate.

Which projects fit Python?

APIs, bots and side projects that must run 24/7 without heavy ops.

If you need horizontal auto-scale or a cluster, talk multi-node instead — support can help scope it.

• HTTP APIs — REST services, webhooks and light backends on a dedicated IP.
• Bots & workers — Discord, queues, long crons — processes that must survive restarts.
• Light SSR — Server-rendered frontends without standing up a full cluster.
• Staging — Cheaper prod mirrors to validate before release.

Python runtime: why 1VPS?

You see RAM, IP and Anti-DDoS. Flat pricing, unified panel, human support — no PaaS black box.

Same network promise as the cloud: Brussels + Peeryx PoPs, public Looking Glass.

• Readable capacity — The plan tells the truth about what the process can consume.
• One panel — Same experience as WordPress, Docker or Linux VPS.
• Simple upgrades — When traffic grows, upscale the plan instead of rebuilding everything.

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 Gitea hosting?

A one-click template on a fixed RAM cloud plan: the app stack is prepared (files, engine, panel access depending on the offer), with NVMe and Peeryx Anti-DDoS. You save deploy time while remaining the application admin.

This is not an opaque “fully managed” SaaS: plugins, themes, updates and tuning stay your responsibility. In return you keep control, a dedicated IP and readable resources — compute in Brussels, Peeryx network PoPs in Paris and Marseille.

• Deploy in ~60 seconds from dash.1vps.cc
• SSL / reverse-proxy depending on the template
• Panel snapshots before a plugin or version upgrade
• Documented network fair-use, Peeryx mitigation included

From selection to first login

The path stays short — without pretending app ops disappear.

1. Select the template — Pick Gitea in the cloud tabs, with the offered version when available.
2. Auto provisioning — The stack starts; panel / files / DB access per offer appear in the dashboard.
3. Customize — Content, extensions, DNS and app backups: you take over on a healthy base.

Which projects fit Gitea?

Concrete cases where the template speeds go-live without locking you in.

If you need a cluster, multi-node HA or full managed ops, we will say so — a root Linux VPS or a support chat is healthier.

• Brochure site — Fast web presence for SMBs, associations or portfolios, editable content and a dedicated IP.
• Content & media — Blogs, docs, file or media sharing — depending on the template capabilities.
• Team tools — Collab, tickets, repos or internal cloud for a small team that wants data control.
• Clear light prod — A predictable RAM plan instead of saturated shared hosting with variable performance.

Gitea hosting: why 1VPS?

A serious template on assumed infra: plan, Peeryx, human support, Belgian company. Limits (fair-use, app admin, one compute region) are stated upfront.

Public Looking Glass to test latency. Migration available if you switch hosts.

• Template + infra, not one without the other — Useful one-click, plus NVMe, IP and Anti-DDoS — not just an installer.
• Honesty about “managed” — You remain admin: we do not sell magical managed service nobody delivers.
• Support that answers — Help on deploy and infra; sizing advice before things get slow.

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.