Skip to main content
Grand Central Integration Platform as a Service (iPaaS) is a pro-code platform that accelerates the development, deployment, and management of banking integrations. The platform provides an engineering-centric environment where you manage infrastructure, application configuration, and deployment workflows through code. Grand Central uses a GitOps approach, so you can self-serve resources, automate deployments, and maintain security standards without waiting on central operations tickets.

Key capabilities

Grand Central is built on enterprise-grade cloud technologies, including Azure and Kubernetes. The platform hosts connectors, APIs, and event-driven architectures while abstracting infrastructure complexity. With Grand Central, you can:
  • Build and deploy connectors: Run integration logic using industry-standard frameworks such as Camel K.
  • Manage APIs: Publish and secure APIs using Azure API Management (APIM).
  • Handle events: Implement event-driven patterns using Azure Service Bus.
  • Monitor applications: View application performance through Datadog or Grafana.

Pro-code approach

Unlike low-code platforms that use drag-and-drop interfaces, Grand Central treats infrastructure as code (IaC). You interact with the platform primarily through Git repositories. This approach provides the following benefits:
  • Auditability: Git commit history tracks every change to infrastructure and application state.
  • Reviewability: Pull request reviews enforce governance and code quality standards.
  • Automation: Merged pull requests automatically trigger pipelines that apply changes. This eliminates manual console operations.

Core repositories

You work with two primary repositories:
RepositoryPurposeUse cases
self-serviceProvisioning control planeManage user access, request repositories, create secrets, and configure platform resources.
applications-liveDeployment control planeDefine runtime configuration for applications across environments (development, staging, UAT) and synchronize cluster state through ArgoCD.
Separating provisioning from deployment creates a clear boundary between infrastructure management and application lifecycle management.

Next steps

  • Architecture: Learn about the platform architecture and components.
  • Key concepts: Understand the core concepts and terminology.
  • Security: Review the security model and access controls.