How this proposal is hosted and managed.

Live architecture

• Public hostname: fisprop.thynkmarketing.com.
• DNS: an A record points only this hostname to 153.75.83.248.
• Runtime: a dedicated nginx container named fisprop.
• Routing and TLS: the existing Traefik service routes only this hostname and obtains its Let's Encrypt certificate.
• Static files are mounted into the container; private deployment files are not in the public document root.
• The existing fad service remains separate and unchanged.

Why we selected this option

Choice	Fit today	Planning cost	Tradeoff
Managed Thynks VPS	Selected and live; uses our known operations workflow	$0 expected incremental	We remain responsible for server patching and monitoring
Cloudflare Pages	Good future option for a dedicated Git-connected static project	$0 expected at this size	Would require a separate deployment and DNS change
Vercel Pro	Useful only if folded into an approved Next.js workflow	Starts around $20/mo plus usage	Unnecessary paid layer for this standalone guide

Main insurance application

This proposal does not decide where the production insurance application will live. Before that cutover, verify the authoritative Git branch, hosting project, database environment, staging separation, backups, and exact DNS destination. The planning allowance for a lean production and staging setup is approximately $55–$200/month, plus $15–$35/year for the domain and $1,500–$3,500 one time for legal/privacy review. Higher usage or added services can exceed that range.

Deploy and rollback

1. Stage only approved proposal files under /root/cockpit-stack/apps/fisprop.
2. Validate the combined Compose configuration.
3. Build and restart only the fisprop service.
4. Verify HTTPS, routes, assets, responsive layouts, and console health.
5. Rollback by removing only the fisprop DNS record and service; do not change fad or email records.