Customer terminology
| Term | Meaning |
|---|---|
| App | One hosted workload on synsmarts. An App has its own configuration and operational surfaces. |
| App slug | The short App name shown in its portal URL and confirmation prompts. |
| Team | The customer workspace that owns Apps, members, billing, and support requests. |
| Framework | The software stack used by an App, such as WordPress, WooCommerce, Magento, Laravel, or Shopware. |
| Deploy | A recorded operation that builds and applies a version of an App. |
| Repository | The connected GitHub repository that can supply a Git-sourced release. |
| Workspace | The managed editable server-side file tree that can supply a Workspace-sourced release. |
| Restore | A managed recovery operation started from the App’s Backups section. |
| Restore slot | The one-at-a-time capacity for restores. Database and folder restores share it, so an App runs a single restore at a time. |
| Vars | The App surface for runtime variables and secret references. |
| Purchased shape | The CPU, memory, and storage amounts bought for an App; they’re the billing and enforcement envelope. |
| Burst | Metered use above a request, without increasing the reserved request. |
| Scheduled job | A command definition the App runs on a schedule, managed in the App’s Scheduled Jobs section. |
Customer-facing pages use App, not tenant or site. Internal identifiers may still contain those older implementation terms; they aren’t customer terminology.