Instance settings
The Settings page lets you change the metadata, capacity, and scheduling of a deployed instance without recreating it. Most changes only take effect on the next start.
Editable fields
| Field | What it does |
|---|---|
| name | Display name shown in the table and the detail header. |
| description | Free-text description. Useful when you have many instances of the same model. |
| serving_name | Public model name. Changing it breaks clients that use the old name; plan a cut-over. |
| gpu_id | Manual mode only. The new GPU is used on the next start. |
| gpu_preferences | Ordered list of GPU preferences. Used as a tie-breaker when multiple GPUs match the model. |
| scheduling_mode | Switch between manual and smart. Smart re-runs provider selection on the next start. |
| smart_region / smart_regions | Pinning or allow-list. Empty means no region preference. |
| smart_max_price_per_hour_usd | Hard ceiling in EUR/h. Null disables the cap. |
| smart_provider_preference | Provider name, ordered list, or empty for cheapest compatible. |
| smart_allow_spot / smart_allow_community | Include non-guaranteed capacity in the selection pool. |
Schedule rules
The Schedule tab on the instance detail page stores cron-based start and stop rules. Rules are evaluated by the scheduler worker using the rule's own timezone.
| Field | Accepted values | Notes |
|---|---|---|
| action | start | stop | What the rule does when it fires. |
| cron | 5-field cron | minute hour day-of-month month day-of-week. Use the platform cron helper if unsure. |
| timezone | IANA tz | All times in the cron expression are interpreted in this timezone. |
| enabled | boolean | Disable a rule without deleting it. |
Examples
0 8 * * 1-5— 08:00 on weekdays.*/15 9-18 * * 1-5— every 15 minutes between 09:00 and 18:59 on weekdays.0 22 * * *— 22:00 every day.Rollback
Every save records the previous values in the audit log. The platform does not currently expose a one-click rollback UI — the audit log entry is the source of truth if you need to reconstruct the state. The runtime configuration snapshot is also stored on the instance and shown in the detail panel.