# GetGeek Documentation > Documentation for GetGeek's services — Swedish, sovereign cloud infrastructure. ## Proxmox Backup - [GetGeek Proxmox Backup](/en/proxmox-backup/index.md): GetGeek Proxmox Backup is a ready-made Proxmox Backup Server destination in GetGeek's own data centre in Stockholm. You point your existing Proxmox VE environment (or your own PBS) at us and get an encrypted, offsite copy of your backups — without having to build and run your own backup infrastructure. The service is built to be the simple, inexpensive offsite copy in your 3-2-1 strategy: three copies of the data, on two different types of media, one of them offsite. GetGeek Proxmox Backup is the third, offsite, copy. - [Getting started](/en/proxmox-backup/kom-igang.md): This guide takes you from zero to a working, encrypted offsite backup at GetGeek. Allow 10–15 minutes. - [Sync from your own PBS](/en/proxmox-backup/push-sync.md): If you already have your own Proxmox Backup Server on site, you can use GetGeek as an offsite copy instead of pointing your Proxmox VE directly at us. Your local PBS then sends its backups to your datastore with us using a push sync job, on a schedule you choose. That is the third copy in another location that the 3-2-1 rule requires, and your existing backup jobs in PVE do not need to change. Requirement: Proxmox Backup Server 3.3 or later (the push direction arrived in 3.3). Some options below require newer versions and are marked accordingly. Allow 15 minutes for the setup. The first sync sends all data and can take hours; after that it is incremental. - [Encryption & key](/en/proxmox-backup/kryptering.md): GetGeek Proxmox Backup uses client-side encryption. It is the single most important property of the service, and it is on by default in Getting started — this page explains what it actually means. - [Retention & schedules](/en/proxmox-backup/retention.md): How long your backups are kept is controlled by a prune policy on the server — it runs for you, and you do not need to configure anything yourself. This page describes the default values and what they actually give you in terms of restore points. - [FAQ](/en/proxmox-backup/faq.md) ## GetGeek Static - [GetGeek Static](/en/static/index.md): GetGeek Static is hosting for static websites built with Hugo. You keep your site in a git repository, just as you do today. Every time you push, we build the site and publish it on your own domain, with HTTPS — without you needing a server, a build pipeline or a CDN account. You look after the content. We look after the build, the servers, the certificates, the updates and the monitoring. - [Getting started](/en/static/kom-igang.md): From order to a live site takes about 15 minutes of your time. After that, publishing happens automatically on every push. - [Manage your site in the portal](/en/static/portalen.md): After ordering, you manage the site yourself on the service page in the portal (Services → GetGeek Static). You don't need to contact us to change domains, roll back a version or replace keys. The status is shown in your account's language. The buttons are currently in Swedish only, so they are given in Swedish below with a translation. - [Connect GitLab](/en/static/gitlab.md): Applies to gitlab.com, GetGeek's Managed GitLab and other self-hosted GitLab instances. You need the Maintainer or Owner role in the project. You need the deploy key and the webhook address from us (see Getting started). - [Connect GitHub](/en/static/github.md): You need administrator access (Admin) to the repository. The repository may be private. You need the deploy key and the webhook address from us (see Getting started). - [Gitea, Forgejo, Codeberg and others](/en/static/andra-git.md): GetGeek Static works with any git service that can give an external party read access with an SSH key (often called a deploy key or access key), andsend an HTTP POST request on push (a webhook). What the webhook sends in the request doesn't matter — we always build whatever is in your branch at that moment. - [Build it yourself with GitHub Actions](/en/static/egen-byggpipeline.md): If you want to build the site yourself — with your own Hugo version, npm, Tailwind, a tool other than Hugo or your own test suite — you can do it in your CI and send the finished result to us. We publish it exactly as it is. Everything else works as usual: your own domain, HTTPS, domain verification, saved versions and an email if something goes wrong. There are two ways. Upload is the simplest: your workflow sends the finished site straight to us. If you would rather have us fetch it from your repository, that works too, via a dedicated branch. - [Hugo at GetGeek](/en/static/hugo.md): Most things work exactly as when you run hugo locally. This is what's good to know. - [Troubleshooting](/en/static/felsokning.md) - [FAQ](/en/static/faq.md) ## DNS - [GetGeek DNS](/en/dns/index.md): GetGeek DNS is authoritative DNS for your domains, operated by GetGeek. Your zone is served by our name servers in Sweden, Finland and the Netherlands. - [Change records with DNS UPDATE](/en/dns/dns-update.md): You can create, change and delete records in your zone programmatically with the standard DNS UPDATE protocol (RFC 2136). Changes are signed with a TSIG key that only applies to your zone. It works with nsupdate, Terraform/OpenTofu, ACME clients and most automation tools. In the examples below the zone is example.se and the key is example-dnsupdate. Replace them with your own values. ## VPS - [VPS](/en/vps/index.md): Virtual servers in GetGeek's own data centre in Stockholm. There are four kinds: All are ordered in the portal under VPS – Virtual servers. Getting started: order and log in for the first time.VPS Cloud: create and remove servers in your pool.Reverse DNS: give the server's addresses a name.Private network: connect your servers.Extra IPv4 addresses: more public addresses on a server.Manage the server: console, new SSH key, reinstall and backups. - [Getting started with VPS](/en/vps/kom-igang.md): How to order a server and log in to it for the first time. - [VPS Cloud](/en/vps/cloud.md): VPS Cloud is a pool of cores, RAM, disk and public IP addresses. You split the pool across as many servers as you like, and create and remove the servers yourself in the portal. You choose the size of the pool when you order. The service itself gets the name you gave it in the cart, for example lab.yourcompany.com. You name the servers when you create them. - [Reverse DNS](/en/vps/reverse-dns.md): Reverse DNS (PTR records) links an IP address to a name. You need it for example if the server sends email, since many receivers check that the sender's address has a name. When a server is created, reverse DNS is set to the server's hostname automatically, for both IPv4 and IPv6. You can change it yourself in the portal. - [Private network](/en/vps/privat-natverk.md): Every customer has their own private network between their VPS servers. It is a layer 2 network: the servers see each other directly, as if they were plugged into the same switch. No other customer can reach it, and it cannot be reached from the internet. All your VPS services are on the same private network, both VPS Bygg själv and VPS Cloud. What differs is how the servers get their addresses: VPS Bygg själv: the server gets a second network card on the private network, without an address. You choose the addresses and set them yourself.VPS Cloud: the service gets its own private /24, for example 10.240.7.0/24. The portal assigns the addresses for you when you create servers. Below is one example for each product, and one for combining them. - [Extra IPv4 addresses](/en/vps/extra-ipv4.md): A server can have more than one public IPv4 address. The extra addresses go on the same network card as the server's first address, eth0, and the server keeps its gateway. - [Manage the server](/en/vps/hantera-servern.md): You do most things yourself on the server's page in the portal. Open the server under Services.