Why We Built Saibius: Creating a File Server with One Command

TL;DR

Introduction

Hello, I'm JunHyeok Seo, CEO of Artsnoa and developer of Saibius.

While building server infrastructure at school and in the lab, I experienced daily frustrations. The repetitive tasks of transferring files between servers and sending files from desktops were incredibly inefficient.

Saibius was born to solve these repetitive frustrations.

Three Questions

1. WHY transfer files via SCP every time?

Entering SSH keys, ports, and paths repeatedly is cumbersome, annoying, and error-prone.

$ scp -i ./my-auth-key.pem -P 8822 \
  ./target-file.tar.gz \
  ubuntu@xxx.xxx.xxx.xxx:/home/ubuntu/deploy/

$ scp -i ./my-auth-key.pem . . .
  ./target-file.tar.gz . . .
  ubuntu@xxx...:/home/. . .

# Sender
$ saibius --file ./deploy
✓ Server running at http://192.168.0.10:3200/

# Receiver
$ wget http://192.168.0.10:3200/project.tar.gz

# Sender
$ saibius --file ./deploy
✓ Server running at . . .

# Receiver
$ wget http://. . ./project.tar.gz

2. Why NGINX for temporary tasks?

What method do you use to share files in your lab or team?

What about mounting ISOs to servers via BMC or ILO? Traditional NGINX requires too many steps: writing config files, opening firewalls.

$ sudo apt install nginx
$ sudo vim /etc/nginx/sites-available/iso-server
$ sudo systemctl reload nginx
$ sudo ufw allow 80/tcp

$ sudo apt install nginx
$ sudo vim /etc/nginx/sites-...
$ sudo systemctl reload nginx
$ sudo ufw allow 80/tcp

$ saibius --file /mnt/iso
✓ Server running at http://192.168.100.5:3200/

# Direct Mount on BMC
http://192.168.100.5:3200/ubuntu-24.04.iso

$ saibius --file /mnt/iso
✓ Server running at ...

# Direct Mount on BMC
http://...ubuntu-24.04.iso

3. Why do all programs require installation?

Most existing software requires additional installation.

Core Design Philosophy

We believe file sharing shouldn't be complicated.