Skip to main content

Plans and limits

YepCode is offered in several pricing plans that scale with your needs.

We offer a generous free tier, so anyone could start to use the platform at no cost. This is the best option for developers that want to try out the platform in a solo approach.

When any user need more executions, more execution time, or want to enjoy the collaboration features working in a team of several members, an upgrade to a higher plan could be done.

Take into account that YepCode is a enterprise-ready platform, and if one client needs to use the platform without exceeding any of the existing limits, we can talk and provide an ENTERPRISE plan version personalized to that company needs.

What are Yeps?

In the YepCode Universe, the concept of Yep represent one process execution.

Each time you run a process in any of the approaches (on demand, using a webhook or with an schedule approach), one Yep is consumed.

Each plan includes an amount of Yeps to be used each month, and at the end of the month, the consumed counter is reset.

In paid plans, if you exceed the amount of included Yeps, you could keep using your account, and each additional Yep will be billed in a pay as you go approach.

Review our pricing page to check each plan amount of Yeps and also the price of each additional Yep in paid plans.

On premise deployments

You may check our on-premise docs page to know more about how YepCode may be used in your system infrastructure.

On-premise versions are only available on GROWTH and ENTERPRISE plans:

In the following sections the GROWTH plan limits are different if the YepCode cloud is used or if client has a executors on-premise installation.

Daily limits

Only the DEVELOPER plan (the FREE one) has daily limits.

These limits are reset every night at 00:00 CET, and include two conditions:

  • Max. use of 300 Yeps by day (that's is 300 process executions).
  • The sum of execution times by day won't exceed 30 minutes.

Max time by execution

Each plan has a limited execution time. If some execution reaches that limit, it will be killed by the system.

PlanMax time by execution
DEVELOPER30 seconds
STARTER5 minutes
GROWTH - YepCode Cloud10 minutes
GROWTH - Executors on-premiseTBD
ENTERPRISETBD

Remember that if you need to skip these limits, we may offer a custom ENTERPRISE plan, and you could be creating services that will be executing as long as you need.

Max team members

One of the main benefits of YepCode are the collaboration features, allowing several developers to share one common workspace of processes and executions, everything with an interesting audit module that allows to see that information.

DEVELOPER plan has a solo approach, but paid plans allow to enjoy that collaboration features.

PlanMax team members
DEVELOPER1 member
STARTER10 members
GROWTHUnlimited
ENTERPRISEUnlimited

Max concurrent executions

The platform restricts the amount of concurrent executions that a team may run.

For example in the STARTER plan, if you already have three active executions, and a fourth one is started, it will be discarded.

PlanMax concurrent executions
DEVELOPER1
STARTER3
GROWTH - YepCode Cloud5
GROWTH - Executors on-premiseTBD
ENTERPRISETBD

Execution result max size

Each execution may have it's own result object. This result will be stored, and will be also be returned to webhooks invocations.

Each log has a max size and a max amount of lines, and if the process execution output exceeds that limits, no more log entries will be saved.

PlanMax result size
DEVELOPER50Kb
STARTER100Kb
GROWTH500Kb
ENTERPRISETBD

Executions history

The execution logs and result will be available for certain amount of time. After that, all the related execution will be removed.

PlanExectutions history
DEVELOPER3 days
STARTER7 days
GROWTH30 days
ENTERPRISETBD

YepCode Forms

The platform restricts the amount of YepCode Forms you can enable for your processes at one time.

PlanAllowed YepCode Forms
DEVELOPER1
STARTER10
GROWTHUnlimited
ENTERPRISEUnlimited

Executions log max lines & size

Each execution may have it's own log that will be available during the execution history period.

Each log has a max size and a max amount of lines, and if the process execution output exceeds that limits, no more log entries will be saved.

PlanExectutions log max sizeExectutions log max lines
DEVELOPER100Kb100
STARTER250Kb250
GROWTH500Kb500
ENTERPRISETBDTBD

Audit events history

The audit module keeps track of everything that is happening on the team (executions, code changes, credentials, webhook invocations...).

These collaboration features are only included in paid plans.

PlanAudit events history
DEVELOPER-
STARTER1 month
GROWTH3 months
ENTERPRISETBD

Command line interface

You may check our command line interface docs page to know more about how YepCode may be used from local workstations.

The CLI is only available on paid plans.

Datastore

You may check our datastore docs page to know more about how to use this simple, fast, and powerful key-value storage system.

The Datastore is only available on paid plans with the following limits:

PlanMax. entriesMax. entry size
DEVELOPER--
STARTER25255 bytes
GROWTH - YepCode Cloud10001Kb
GROWTH - Executors on-premiseTBDTBD
ENTERPRISETBDTBD

Identity brokering

If your company wants to use an external identity provider, we may offert that using OpenId or SAML protocols.

These kind of integrations are only available on GROWTH or ENTERPRISE plans.

Users federation

Another option regarding to authetication is to provide users federation with LDAP or Active Directory.

This will be only available on ENTERPRISE plans.