Skip to Content
đź‘·Please note that Dboxed is in a very early stage, including the documentation. Things are being built right now! đź‘· Follow @codablock on X for updates!
DocsMachines

Machines

A machine is a server that is able to run boxes. Dboxed tries very hard to keep the requirements for such servers as low as possible, allowing you to use any kind of server. The only requirements dboxed has on a server is a recent Linux Kernel, internet and root access.

Here are some examples of server types you may use:

  1. Hetzner Cloud Servers 
  2. Hetzner Dedicated Server 
  3. AWS Instances 
  4. All other cloud providers that offer VPSs
  5. Servers from your own your datacenter
  6. Your single Server(rack) in your company office
  7. Your Raspbery Pi
  8. Inside Docker Containers (including on your Mac, even though it will be slow)

Networking

Dboxed only requires an outbound internet connection for its basic functionality. It does not require you to have private networking (e.g. AWS VPC  or Hetzner Cloud Network ) to work, as it uses P2P VPN solutions (like Netbird ) for its private network abstraction.

At the same time, it will leverage such private networks when detected to optimize for speed and reduce traffic costs.

See networks for more details.

Persistence

Dboxed uses dboxed volumes for persistent storage. These volumes do not require support from the underlying cloud provider (if you’re even running on a cloud server) and work on all machine types.

See volumes for more details.

Machine Providers

Machine Providers are not fully implemented yet. Stay tuned for updates.

Dboxed allows you to dynamically create machines from the dboxed CLI and the Web UI. This means that you do not have to provide machines by yourself, but instead can rely on dboxed creating these fully automatically for you.

Currently, AWS and Hetzner are supported. Future versions of dboxed will support many more providers.

Last updated on