Deploying Pega Infinity 25.1 for demos

What is the smallest deployment of Pega Infinity 25.1 possible for building demos / proof-of-concept etc. purposes? From documentation provided I still see “Hybrid Deployment” mentioned in Pega Labs 25.1 instances making me think it is still possible to deploy 25.1 on a local Tomcat instance. If this is not possible, what is the smallest possible deployment if I already have shared externalized services setup in a local / partner cloud environment?

@Dhammike

Pega Community Edition 30–45 day rapid prototyping.You can sign up via the Pega Community and typically get a 30-day instance (extendable by 15 days) that includes the latest Infinity 25 features.

Thanks RameshSangili and we all use community instances but there are many times a partner may need to try the build/PoC within the organization’s infrastructure unless you are already using dedicated Pega Cloud instances for that work. This is why I’m trying to see how I can replicate something similar to Pega Labs but within the organization’s infrastructure.

I believe that Pega Labs might be the smallest possible deployment, and that environment is an open-source based stack.

It certainly is Phil and unless the documentation is outdated it still shows 25,1 running in hybrid-deployment where is it deployed in a single VM. That’s why I’m trying to see how I can replicate the same within the organization-managed Cloud for use in enablement and Proof-of-Concept development etc.

Hi @Dhammike ,

I manage Pega Labs and can help clarify this.

The “hybrid deployment” references in Pega Labs documentation apply to an older, Labs only architecture that deployed Pega on a single VM. That model is not intended as a reference architecture for customer or partner managed environments.

For Pega Infinity 25.1, we support both hybrid and Kubernetes based deployments, and users can switch between architectures via self service. In Pega Labs, the Kubernetes architecture is implemented on a single VM, with Pega running in Kubernetes. External services such as Cassandra, Kafka, and search remain external to the Pega application, but in Labs they are typically hosted as Docker containers on the same VM for simplicity.

Community Edition and Trial environments use this same Kubernetes based architecture. There is no supported local Tomcat only deployment model for 25.1 that mirrors Pega Labs behavior.
If you already have shared external services in a managed cloud, the smallest comparable setup would still be a Kubernetes deployment, potentially a minimal or single node cluster depending on your tooling. Pega Labs is optimized for demos and PoCs and cannot be directly replicated using a traditional application server model.

If the goal is to support multiple demos or PoCs at scale, another option may be expanding access to Pega Labs rather than rebuilding this internally. Happy to discuss based on how many environments you are looking to support.

Resources:
Pega Labs Community Page (Customers and Partners can request access.)

Matteo

2 Likes

Thanks Matteo for the detailed response. Since mine was going to even lengthier I responded to you direct but not sure if that ended up in spam.