Running and scaling an app

Size, scale, monitor, and cancel a live app. Plan and scaling changes need the Technical role, owner, or admin. Cancelling an app needs owner or admin. Read-only members can view every tab.

The Billing tab shows the current plan, the next invoice, and this app's invoices.

1. Click Switch Plan.
2. Pick a plan. Cards list CPU, memory, included replicas, bandwidth, and features.
3. Under When to apply, choose Immediately or At next cycle, if your organization allows a choice.
4. Confirm with the slide control.

A plan below the app's recent usage triggers a warning and may be refused. A plan that does not fit location capacity is refused. Moving to Free requires a card or PayPal on file. A dimmed control with an upgrade note means the plan lacks that feature.

synteq app plan show
synteq app plan change pro

A replica is one copy of the app in its own microVM. Traffic is spread across replicas, so the app must be safe to run as several instances.

Set the count on Settings → Scaling. The plan caps the count; the note shows included replicas and the price of extras. New instances pass the health gate before taking traffic.

Autoscaling adds or removes capacity within a monthly budget. It needs a plan that includes it, never Free, and may carry a monthly fee, billed only while on.

1. On Settings → Scaling, turn on Autoscaling.
2. Set Max autoscaling budget /mo. The panel shows what it buys.
3. Set Target CPU % and Target Mem %. Usage above these triggers scaling.
4. Choose Preferred scaling.
5. Click Save.

Some plans fix the direction. The engine runs every few minutes; Recent scaling events lists each change and its trigger. A banner shows when the plan ceiling or budget stops scaling. A manual replica count overrides.

Settings → Locations shows the primary location and Location mode.

Multi-region and Edge need a plan that includes them and may carry a monthly fee, sometimes one bundle for both.

1. Set Location mode to Multi-region or Edge, and confirm any fee.
2. Click Add a location and pick one.

Each placement shows its own status and is billed on its own line at the plan's rate.

Multi-region needs two live locations: a healthy placement that would leave one cannot be removed, but a degraded one can. Single-region requires only the primary to remain.

The Usage tab charts CPU, memory, and bandwidth against the allowance, from 15 minutes to a week. A banner shows while the app is over.

Each axis (CPU, memory, bandwidth) has a plan rule:

Throttled memory restarts the app at the cap.

Overage shows under Accrued this period on Usage and under Overage charges this month on Billing, and is added to the next invoice. When usage exceeds your plan, Billing suggests the cheapest plan that fits it.

The Logs tab is a live tail. The chevron on its top edge toggles near full-screen.

• Each line has a timestamp, release, instance, and level. Platform runtime output is not shown.
• Filters has search, Console level, Timeline, and Build version. Unloaded windows are fetched from history, within retention (see Apps overview).
• Scroll to the top for older lines. Clear buffer and refresh restarts the tail.
• Export logs copies lines or downloads CSV or JSON.

synteq app logs -f                # live tail of the linked app
synteq app logs my-api            # the last hour of history
synteq app logs --since 1h --search error
synteq app logs --from 2026-09-12T16:00:00Z --until 2026-09-12T16:30:00Z -o json

synteq app logs queries history; -f or --follow tails live instead. History takes --since (default 1h), --from and --until (ISO timestamp or age such as 3h), --search, --container, and --limit (up to 5000).

When Console is available, Console in the app header opens a shell in the running container. It is not available on Free. Filesystem changes are lost on the next release. Activity records when each session opens and closes.

The Overview tab shows:

synteq app metrics --range 24h
synteq app health

The Activity tab records every deploy, rollback, variable change or reveal, domain, plan, and scaling change, console session, skipped push, and cancellation, with who and when.

1. On Settings → Danger zone, click Cancel app.
2. Pick a reason, add an optional note, and confirm with the slide control.

The app runs until the period ends and does not renew. No refund or proration is issued. Before then, click Undo on the banner at the top of the app page to un-schedule it.

Afterwards the app stops and its hostname stops resolving. Contact support within seven days to recover it. Only support can reverse a cancellation support scheduled.

• Deploying and configuring an app: builds, variables, domains, and rollbacks.
• Apps overview: how apps run, networking, and limits.
• CLI reference: every synteq app command.