PCF Elastic Runtime

A Complete, Scalable Runtime Environment for Modern Apps

Run cloud-native apps in a full-featured runtime. Elastic Runtime (ERT) gives developers a consistent and reliable mechanism for application deployment and operation. Deploy your code. ERT automatically adds dependencies, creates a container, manages networking, and binds specified backing services. From there, it manages container orchestration and scaling, while emitting logs and metrics for easy consumption.

Focus on Your Code—and Let ERT do the Rest

When you deploy new code with a simple cf push, ERT gets it to production for you. Dependency management, load balancing, container orchestration, logging and auditing are done for you!

Container Management and Orchestration Made Easy

When you push your code to ERT, it automatically containerizes your app. You can focus on increasing feature velocity, not managing container images. This approach also helps you know what’s running in production. What’s more, the platform helps keep the base file system up to date to recent security patches. It’s much easier to meet corporate security standards with automated container creation.

Unified Metrics & Logging Ease Troubleshooting

ERT includes vital monitoring and logging capabilities. Developers and operators have a central stream of reliable metrics to help identify issues quickly.

Pivotal Cloud Foundry Overview


PCF Elastic Runtime is a full-featured runtime environment, extensible to most modern frameworks or languages running on Linux. Deployed applications enjoy built-in services and can automatically bind to new data services through a service broker or to an existing user-provided service.

How it Works

The Elastic Runtime architecture is composed of a load balancer, routers and applications. Platform customers interact with Pivotal Cloud Foundry through a simple command line interface (CLI), the “cf cli”. The cf push command is simple, but it does a lot for your code. When you cf push your application code and a few parameters, ERT automatically:

  • Uploads your application code
  • Determines and installs the correct runtime and middleware to run your application
  • Sets up a route (or URL), creates a load balancing entry and creates SSL termination for your application
  • Creates health monitoring and logging subsystems and starts your application in a healthy state with the desired number of instances
  • Binds any backing services needed to your application by injecting the service credentials

To flexibly serve and scale apps online, ERT has subsystems that perform specialized functions. A few of these components are:

  • Traffic & Routing - CF Cloud Controller runs the apps and other processes on the cloud’s VMs, balancing demand and managing app lifecycles. The router directs incoming traffic from the world to the VMs that are running the apps that the traffic demands, usually working with a customer-provided load balancer.
  • Communication within ERT - components communicate with each other by posting messages internally using http and https protocols, and by sending NATS messages to each other directly.
  • Monitoring & Analysis - As ERT operates, the Cloud Controller VM, router VM, and all VMs running apps continuously generate logs and metrics. The Loggregator system aggregates this information in a structured, usable form, the Firehose. You can use all of the output of the Firehose, or direct the output to specific uses, such as monitoring system internals or analyzing user behavior, by applying nozzles.
  • Role-Based Access Controls - To organize user access to the cloud and to control resource use, a cloud operator defines Orgs and Spaces within an installation and assigns Roles such as admin, developer, or auditor to each user.

Read the documentation

Get Started

Contact Us
Thank you for your interest!

We will get back to you shortly.