Skip to content

Operations

This page covers the Gradio service, backups, moving to another image, and support.

Security model

  • Loopback only. The page listens on port 7860 on the instance. You reach it by forwarding that port to your workstation.
  • Sign-in. First boot creates /home/ubuntu/.config/sushi-gradio/access.json with mode 0600. The queue API used by sushi-gradio reads that file.
  • Non-root service. sushi-gradio.service runs as a non-root user.
  • Local model. The starter does not send text to a model provider.

Service

sudo systemctl status sushi-gradio.service
sudo systemctl restart sushi-gradio.service

Restarting keeps the first identity and the rows already stored in /var/lib/gradio/predictions.sqlite3.

Backups

Back up these together while writes are stopped, or from a consistent snapshot:

  • /var/lib/gradio
  • /home/ubuntu/.config/sushi-gradio/access.json
  • ~/gradio-results

The database without the access file leaves you unable to sign in as the same account. The access file without the database drops the saved predictions. Preserve ownership and modes.

Updates

A new Marketplace version is a new instance. Launch it, restore the three items above, and run sushi-gradio read on a saved JSON file before you treat the new instance as ready. Do not delete identity files to make first boot run again.

Support

Software Sushi provides AMI packaging and setup guidance. Email info@softwaresushi.com for installation questions. Include the Marketplace version, the Region, and the command you ran. Omit the contents of access.json.

The software rate on the listing is USD 0.03 per running instance-hour. EC2, EBS, and data transfer are separate. The local starter has no model-provider usage charge. Support beyond installation questions needs a separate agreement. Upstream Gradio support is not included. The offer uses the AWS Marketplace Standard EULA. See the offer for legal and refund terms.

Last updated October 27, 2026 · Suggest an improvement