Skip to content

Plans and limits

Compare Free, member, and new-account limits.

Applies to
CLIConsoleAPI

Verified · v1.4.16

Markdown

You can use Free limits with an AGI Lab account. Active AGI Lab members get higher limits at no extra charge. Wings has no standalone paid plan. See current membership pricing for the membership fee.

Standard limits

Resource Free AGI Lab member
Handlers 10 200
Connections 100 100
Databases 3 50
Total Database storage 512 MiB 7.5 GiB
Triggers in total 10 200
Triggers per Handler 10 10
Web Apps 3 20
Minimum Schedule interval 5 minutes 1 minute
Runs per minute 10 30
Runs per hour 50 300
Combined enabled Schedule runs per hour 50 300
Maximum duration of one Run 30 seconds 120 seconds
Run duration per UTC day 30 minutes 90 minutes
Database rows scanned per day 1,000,000 1,000,000
Database rows written per day 20,000 100,000

Each Handler's source can be up to 500 KiB. There is no daily Run count limit; the daily limit is based on elapsed time.

Web App Runs do not count toward per-minute or per-hour Run limits. They still use the daily time allowance and have separate Web limits. API Triggers also have request and concurrency limits.

The first 7 days

A new Free account has the following limits for 7 days from its first use of Wings. All other limits match standard Free limits.

Item First 7 days
Handlers 3
Triggers in total 3
Triggers per Handler 3
Web Apps 1
Minimum Schedule interval 15 minutes
Run duration per UTC day 10 minutes
Runs per minute 5
Runs per hour 20
Databases 1

Standard Free limits apply automatically after 7 days. Anything you created remains in place. These first-week restrictions do not apply to members.

When membership ends

Handlers, Schedules, and Databases are kept. Schedules no longer run more often than the Free minimum interval. Resources above the new count limits remain in place. New creation and some writes that increase storage are restricted. You can still update or remove existing Handlers.

Combined hourly Schedule limit

Enabled Schedules count toward this limit as follows:

  • An interval counts as 60 minutes divided by its interval.
  • A cron Schedule counts as its busiest hour on an ordinary day.
  • A one-time Schedule counts as one until its time has passed.

Daylight saving changes and recent edits can make actual Runs differ from that count. Actual Runs must also stay within the per-minute and per-hour limits.

Use wings usage or the Console to check your current usage and limits. If your account has custom limits, those take precedence.