Quick Start¶
Strawly runs in Docker. Pick the guide that matches where you want to run it:
| You want to | Guide | Time |
|---|---|---|
| Try Strawly on your own computer, with sample data | Try Strawly on your computer | 10 minutes |
| Run Strawly for real on a server, with a domain and HTTPS | Deploy on a server | 15 minutes, plus DNS |
| Run Strawly on a TrueNAS box at home or in the office | Deploy on TrueNAS | 15 minutes |
| Run separate Strawly instances on one server, for example one per client | Multiple instances | 5 minutes per instance |
| Wire Strawly into your own Docker setup and reverse proxy | Manual install | 20 minutes |
Every guide ends the same way: you open Strawly in a browser, sign in with the admin account the installer created, and choose a new password.
Moving from a test to a real server¶
Anything you set up while testing can come with you. On the test instance, download a backup from Settings > Database Usage. Install Strawly on the server, sign in, and choose Restore from a backup when Strawly asks. See Backup and Restore.
Loading demo data¶
Local test instances can load a fictional Azure estate with six months of history: about 110 resources across three subscriptions with daily metrics, around 55 recommendations at every stage from new to implemented, realized savings, three initiatives and the collector run log. It also adds two demo accounts: admin@strawly.app with password admin123, and viewer@strawly.app with password viewer123. The installer offers it, or run it later:
Because those passwords are public, Strawly allows demo data only on local instances, which nobody else can reach.