Operations¶
This page covers day-to-day care of Langflow 0.2.1: access, backups, moving to another image, and support.
Security model¶
- Loopback editor. The UI is on
127.0.0.1:7860. You open it through Session Manager or an SSH tunnel. Leave port 7860 closed to inbound traffic. - Administrator login. First boot creates
/etc/langflow/admin.json. Signup and automatic login are off. - Encryption and identity.
/etc/langflowholds the original encryption material and the administrator identity. Generating a replacement key can make stored credentials unreadable. - Your provider key. You add it after launch in a mode
0600file. Flow exports can contain provider configuration. Inspect an export before you share it.
Status and logs¶
sushi-langflow status
sudo journalctl -u langflow.service --no-pager -n 100
sudo systemctl restart langflow.service
Backups¶
Stop Langflow before a filesystem backup, or take a consistent SQLite snapshot. Back up these together:
/var/lib/langflow(includinglangflow.db)/etc/langflow(includingservice.env,admin.json,initialized.json, and anyoperator.env)
Restore the database with its original encryption and administrator configuration. Keep the backup until you have opened the editor and run a flow you trust.
Updates¶
A new Marketplace version is a new image. Keep a consistent backup, launch
the replacement, and restore /var/lib/langflow and /etc/langflow
together. Do not create a second administrator identity as a substitute for
that backup.
Support¶
Software Sushi provides packaging and setup guidance. Email
info@softwaresushi.com with the Marketplace
version, the Region, and what you ran. Do not include admin.json, the
encryption material, or the provider key.
The software rate on the listing is USD 0.03 per running instance-hour. EC2, EBS, data transfer, and model-provider calls are separate. Support beyond installation questions needs a separate agreement. Upstream Langflow support is not included. See Software Sushi for the company site.
Last updated November 1, 2026 · Suggest an improvement