Upgrade your jobs with a subscription

The Runly core packages are open source and MIT licensed. Build, run, and distribute your application as you see fit.

The subscriptions below allow you to take advantage of the Runly Platform to shepherd your jobs from deployment to monitoring and scaling in production.

Individual

Free

For developers with personal or hobby projects. Best for learning and experiments.

Schedule and run your background jobs on your own hardware or the cloud.

Push your code and go!

Get started
Hobby

$9

/mo

Collaborate with a friend on hobby or personal projects.

All the Individual features plus:

  • 2 included user accounts
  • Integrate your backend and frontend applications using the Runly API

Get started
Team

$49

/mo

For small teams with production workloads.

All the Hobby features plus:

  • 5 included user accounts
  • Role-based access control
  • Multiple development environments and node clusters

Get started
Professional

$149

/mo

For larger teams with more complex infrastructure requirements.

All the Team features plus:

  • 10 included user accounts
  • Granular role-based access control
  • Up to 4 development environments and node clusters

Get started

Don't see what you're looking for?

Contact us and we will come up with a plan to meet the needs of your business.

Feature Comparison

From solo work to enterprise teams with advanced infrastructure
FeatureIndividualHobbyTeamProfessional
Included team members12510
Multiple ownersNoYesYesYes
Ops security role
Learn more about role-based access
NoNoYesYes
Developer security role
Learn more about role-based access
NoNoNoYes
One-step deployment to worker nodes
Upload jobs as nuget packages via the dotnet/nuget CLIs or the Runly web app.
YesYesYesYes
Automate continuous delivery scenarios
Setup your CD server to automatically push your jobs to Runly.
YesYesYesYes
Schedule jobs
Queue your jobs to run automatically on a schedule.
YesYesYesYes
Run nodes on bare metal or the cloud
Run worker nodes from your machines or anywhere that supports docker.
YesYesYesYes
Integrate your app
Schedule, run, and get results of jobs in your frontend or backend apps.
NoYesYesYes
Job templates
Save job configuration per environment and create schedules.
1 / env5 / env10 / env50 / env
Concurrently connected nodes
The maximum number of worker nodes that can connect to your organization at any one time.
12816
Environments
The number of development and production environments.
1124
Clusters
A cluster is a group of related nodes.
1124
SupportCommunity SupportEmail SupportPriority Email SupportPriority Email Support

Frequently Asked Questions

Do you offer a free trial for paid plans?

You can get started for free on the Individual plan and use that for as long as you like. Only pay once you outgrow the free plan.

There is no free trial version available for paid plans. However, if you aren’t satisfied for any reason after upgrading to a paid plan, send us a message and we’ll make it right.

What is a cluster/node?

Nodes are machines connected to your organization that run jobs. You can run a node on a physical machine, a virtual machine, or in a docker container. A cluster is a group of related nodes. Checkout our documentation for an overview of how Runly works.

Does Runly host nodes?

No, Runly does not host any nodes. The node count that is a part of each plan is the limit on how many simultaneous nodes are allowed to be connected to your organization at any given time. All nodes within your organization are hosted by you. You can run your nodes on a variety of operating systems and in the cloud via Docker.

Can I distribute software I build with Runly?

Yes, any software you build on top of the Runly platform can be used in commercial and/or proprietary applications. All of the Runly packages that you build your application upon are completely open source and covered by the MIT license.

How is the node count computed?

A node is counted toward your plan limit if it is connected and listening for jobs to run. Once a node disconnects, it is no longer counted toward the plan limit. When a node connects and your plan’s node count is exceeded, the node will be allowed to connect while the earliest connected node becomes deactivated. The deactivated node will log a warning when this happens. If another node disconnects, the deactivated node will reactivate.

Still have questions? Ask us.

Ready to try Runly?