diff --git a/Fly.io.md b/Fly.io.md
index a00474c..f6fa6a5 100644
--- a/Fly.io.md
+++ b/Fly.io.md
@@ -5,6 +5,7 @@ No IaC story at the moment. Had a previous terraform provider but was discontinu
 ## [Pricing][1]
 
 There is no "free allowance" on new fly.io plans (referred to as "Pay As You Go"), instead, you pay for compute resources as you use them.
+However bills that accumulate a usage of less than US$5.00/mo are currently waived.
 
 For the majority of apps, fly machines in the `shared-cpu-1x` category will be sufficient.
 As an example, for a near-stock Rails app that was deployed to the Sydney region, the resources created were:
@@ -16,5 +17,37 @@ As an example, for a near-stock Rails app that was deployed to the Sydney region
 Apps that are shutdown but persist on Fly.io accumulate a RootFS storage fee of $0.15/GB/month—this covers the cost of the file system, and is based on your OCI image generated from your app.
 [This change took effect from April 2024][2].
 
+## Deployment
+
+An example deployment flow using `fly.io` for a Ruby on Rails app.
+
+### Integrating secrets
+
+`flyctl launch --no-deploy`
+
+Add TAILSCALE_AUTHKEY secret
+Add RAILS_SECRET_KEY_BASE secret
+
+`flyctl deploy`
+
+https://community.fly.io/t/setting-secrets-before-the-first-deployment-does-nothing/5589/7
+
+
+### Runtime secrets
+
+
+### Networking
+
+Apps created with Fly.io are immediately assigned an IP address and provided with a `.fly.dev` domain name.
+The public-facing IP address can be removed via either `flyctl` or through the GUI.
+
+TODO:
+
+https://fly.io/docs/blueprints/private-applications-flycast/
+https://fly.io/docs/blueprints/connect-private-network-wireguard/
+https://tailscale.com/kb/1132/flydotio
+https://community.fly.io/t/accessing-an-external-non-public-resource-from-your-fly-io-app/10180
+https://community.fly.io/t/connecting-your-fly-apps-to-your-tailscale-tailnet/17828
+
 [1]: https://fly.io/docs/about/pricing/
 [2]: https://community.fly.io/t/we-are-going-to-start-collecting-charges-for-stopped-machines-rootfs-starting-april-25th/17825