S3 object storage, backups and databases as products you sell
Every hosting client has data they need to keep somewhere and restore from something. Flaem lets you sell them S3 space, a backup disk and managed databases, and keep backups of their servers, VPS and sites wherever you decide: on the node, on a separate disk, in a second location or on their own cloud drive.
Game server backups: incremental, on the node and off it.
S3 object storage, sold like any other service
Object storage is a place for files that applications write to over the internet, with no disk attached to a server. The client buys S3-compatible space from you and plugs it into any tool that speaks that standard.
Buckets and keys in the panel
The client creates buckets and access keys on their own, without a ticket.
S3 compatible
Works with libraries, backup software and applications that already speak S3.
Your disks, your price
You choose which disks hold the space and set the packages and prices.
On when you want it
Object storage is a separate kind of offer. It appears in the store only once you switch it on.
Storage box: just a disk for backups, with no OS to maintain
Some clients do not need a server, only a place to send their backups every night. A storage box is a disk reachable over the network, with no operating system to update and secure.
You put storage boxes on the disk you choose, such as large HDDs, and not on the same fast disks your VPS run on.
A client who wants a small CPU and a big disk with their own OS gets a regular VPS package. A storage box is for those who only want the space.
VPS backups on the node, on a separate disk and in a second location
A backup that sits on the same disk as the machine disappears with it. That is why you set where each package keeps its backups, and the client can add a spare backup in another location.

Where backups go is decided in the wizard when you add a node or a package.
Incremental game server backups, with shared files stored once
Servers of the same game mostly share identical files. Flaem stores them on disk once, and every later backup holds only what changed since the previous one.
- Backups include the server databases, in the same archive
- Restore the whole server or only selected files
- Download a backup as zip or tar.gz
- Daily, weekly and monthly retention set in the package
Backups to the client cloud drive and single-file restores
Some clients want a copy on their side too. They connect their cloud drive in the panel, and backups of their services land there next to yours.
- world/
- region/
- playerdata/
- plugins/
- config.yml
- server.properties
- server database
- Client cloud drive
- The client connects their cloud account, and backups of their services land there too.
- Selected files from a backup
- For games, sites and VPS the client restores only the files they need instead of the whole service.
- Files, databases or both
- A backup covers the databases attached to the service, and the restore asks what should come back.
- Backup to download and upload
- A zip or tar.gz archive, also larger than 4 GB. The client can upload their own archive too, such as one from a previous host.
- Website file history
- For websites every file change is visible and each one can be rolled back.
Managed MySQL, MariaDB and PostgreSQL databases
The client gets a database their application connects to, not a database server to administer. Access, backups and limits live in the panel, and you decide which machines the databases run on.
- MySQL
- MariaDB
- PostgreSQL
Where databases run
- Database browser
- The "Open" button logs the client into a database browser with one-time access, without installing phpMyAdmin for good.
- Large dumps
- Importing a dump of any size runs in chunks, with progress and an error report. Export downloads in one click.
- Backups consistent with data
- The database dump goes into the same backup as the service files, so a site and its database come back from the same moment.
Client database statistics: size, queries and locks
A database that is about to slow down usually warns you first: it grows, collects more slow queries or hits its connection limit. The client sees it in their panel, and you see every database on every host.
You see: the database host and a ranking
The load on every database host and a ranking of the databases that use it most, so you know straight away which one slows its neighbours down.
- Database 1
- Database 2
- Database 3
- Database 4
- Database 5
Client data on your disks and under your rules
Space, backups and databases are products like any other: you decide which hardware they live on, what they cost and how long you keep backups.
- VPS and game servers
- Databases
- Backups
- Storage boxes
- S3 object storage
- A disk for every product
- On one node every product can use different disks: backups and storage boxes on large HDDs, machines and databases on fast disks.
- Retention and schedule per package
- How many backups, how often, at what time and for how long is set separately for every package.
- More space comes with the package
- Clients do not add single gigabytes to a service. When they need more, they move to a bigger package or get a custom offer from your staff with a payment link.
- Disk usage map
- For every service you see what takes up space and how fast the data grows.
- Backup of the whole installation
- The panel itself is backed up too: the whole Flaem installation on a schedule.
Questions about object storage, backups and databases
S3, storage boxes, VPS and game server backups, and managed databases.
Yes. The client plugs it into any library, backup tool or application that supports S3, using access keys from the panel.
A storage box is just a disk, with no OS for the client. They reach it over SFTP, rsync, SMB or borg and have nothing to update. A VPS with a small CPU and a big disk is a regular VPS package.
On the node where they were made. For a package you can also switch on a backup on a separate disk, off the node (S3, SFTP, Proxmox Backup Server) or in a second location, in "only there" or "here and there" mode.
MySQL, MariaDB and PostgreSQL. You decide whether they run on regular nodes or on separate machines.
Yes. The client ticks the databases attached to the service, a consistent dump goes into the same archive, and at restore they pick files, databases or both.
Not in single pieces. More space means a bigger package or a custom offer from your staff with a payment link.
Yes. They connect their cloud drive in the panel and backups of their services land there too.
Read next
- Dedicated servers: machine inventory, iPXE and console
- GPU servers and AI models on your own cards
- Proxmox VPS panel: snapshots and moves in seconds
- Game server panel: backups, schedules and 36 games
- Web hosting and apps: WordPress with restore points
- Monitoring and statistics: data retention and capacity reports
- Every Flaem feature on one page
- Flaem licence pricing: per node and per option
We will show backups, S3 and databases on your hardware
Tell us where you keep client backups today and which databases you sell. We show off-node backups, storage boxes and managed databases, then work out the licence from the price list.