Platform limits
Technical limits for what can be configured and run in Waysayer.
This English version is a translation provided for convenience. The Norwegian version is the authoritative text; if the two differ, the Norwegian text prevails.
This page is referenced from the Customer Terms section 7. The Order Form names the plan and refers to the product page, which sets out the included volume. Platform limits apply in addition, but do not reduce what the plan includes (Customer Terms section 7).
Last updated: 15 October 2026
Waypoints
Waypoints measure the work the platform’s resources perform for the customer, where and when it happens, including time spent waiting for other systems to respond. Where one operation starts another, the work in both is counted. Waypoints measure work, not a fixed amount of time.
| Limit | Value | Note |
|---|---|---|
| Operation | At least 0.1 Waypoint | An operation is one run of a resource, for example a Way run, a call to a Path, a call to a platform function that runs on its own (such as data operations, documents and files) or an action from the portal. Steps the Way performs itself are part of the Way run and are not counted separately. Each operation uses at least 0.1 Waypoint. An operation lasting longer than one second uses 0.1 Waypoint for each second or part thereof, including time spent waiting for other systems to respond. |
| Weight per operation type | 1 for standard operations | Operations that run with more memory or capacity get their own weight. The weight is listed here, or stated when the component is configured, for example when a Path is set up with more memory. Changes to the weight of operations already in use are notified at least thirty (30) days before they apply. The same applies when something already in use starts to be counted as an operation. |
| Failed calls and retries | Counted as normal use | Failed calls to the customer's own systems and automatic retries are counted in the same way as other operations. |
| Recording of usage | Continuous, not real time | Usage is recorded continuously, including writes to the lookup store. Use that occurs before a limit or a stop takes effect is counted as normal usage. |
Lookup store
Stored rows and writes have their own allowances, which follow the plan.
| Limit | Value | Note |
|---|---|---|
| Writes | One per row | Each row written or deleted counts as one write, including a write that changes nothing. The monthly allowance follows the plan. |
| Retention and deletion | Until the rows are deleted | Rows in the lookup store are kept until they are deleted, by a Way or through the API. They do not follow the run history's retention. When the agreement ends, they are deleted as set out in the Customer Terms. |
| Stored rows | Across all tables | Rows in all lookup-store tables are counted together. The limit follows the plan. |
Configuration limits
The limits below apply where the relevant function is included in the subscription. The values are defaults and apply unless otherwise agreed in the Order Form. Fastpath states the current values for a workspace on request.
| Limit | Value | Note |
|---|---|---|
| Custom entities | 5 per workspace | Unless otherwise agreed. Requires that custom entities are included in the subscription. |
| Custom fields per entity | 25 per entity | Unless otherwise agreed. Applies per entity definition. |
| Active Paths | As set out in the plan | A Path is the connection to one system in one environment. Paths for test and production both count. Requires that integrations are included in the subscription. |
| Active Ways | As set out in the plan | Active Ways are Ways started from outside: by a Gate, a schedule or a button. Ways started only by another Way, drafts and Ways that are switched off do not count. Requires that integrations are included in the subscription. |
| Chained Ways | Up to 3 × active Ways | Ways started only by another Way. They do not count as active Ways. |
| Schedules | Start time not guaranteed | Schedules are mainly meant to control how often recurring Ways run, not exact times. Planned times may be adjusted and spread within a nearby time window to balance the load, and the run itself may start later than planned. The shortest interval follows the plan. Exact or fully fixed times by agreement. |
| Gates | As set out in the plan | A Gate receives webhooks and API calls and starts a Way. |
| Calls per second per Gate | 20 | Calls above the rate are rejected with a request to retry. A higher rate by agreement. |
The fact that a value is not published on this page does not mean that the matter is unlimited.
Limits that are not published
Waysayer additionally has technical and operational limits that follow from the platform’s architecture and from the underlying cloud services. These are not exhaustively published, and this page is not a confirmation that anything not listed here is unlimited.
If such a limit becomes practically relevant to a customer’s use, Fastpath informs the customer. If it is set as a general limit, it is published here.
Changes
New limits. Fastpath may introduce limits that have not previously been published. Such limits apply from publication on this page. If Fastpath is aware that such a limit restricts a customer’s existing use, Fastpath notifies the customer separately.
Changes to published limits. If a published limit is increased, it applies from publication. If a published limit is tightened so that it restricts a customer’s existing use, Fastpath gives the customer at least thirty (30) days’ notice, and section 16 of the Customer Terms applies accordingly.
See also the Standard terms.