basis relay
Connected systems. Code you own.
Connect SAP, business applications and partners with basis relay. Your team owns the integration code. basis builds it, delivers it from dev to production and runs it.
- Your code, your repository
- Dedicated installation
- Dev to prod
Inside basis relay
One dashboard, from commit to message.
Integrations, message flow and failed messages across every environment, at a glance.
Each push is built, tested and published as one version, then promoted from dev to test to prod.
Every promotion with its reason. Production waits for an approval from someone else.
See why a message failed, and resend it with a written reason that is kept in the audit log.
Instances, delivery state and logs for each environment, without access to the cluster.
Is this for you?
- 01
Your systems must exchange data reliably: SAP, business applications, partners and new services.
- 02
You want integration code your team owns and understands, not a black box.
- 03
You want to see every message, and resend the ones that fail.
basis relay
Integration code you own. A platform we run.
- 01
Connect the systems you depend on
Integrations are ordinary application code in your own Git repositories. Start from a template, or import a repository you already have.
- Code and repositories remain yours
- Templates for Camel Quarkus and .NET
- HTTP, files, databases and messages
- 02
A managed foundation
relay runs as a dedicated installation on Kubernetes, not as a shared service. Each integration runs in its own namespace, with its own database and broker identity.
- Builds, delivery and configuration run by basis
- Operations and recovery handled by basis
- Promotions, changes and resends recorded with who and why
- 03
Yours to keep, ours to operate
Your team owns what an integration does. basis owns the machinery around it.
Yours to keep
- Source code and repositories
- Business logic, mappings and tests
- Credentials and business data
Ours to operate
- Builds, images and delivery
- Configuration and platform identities
- Operations and recovery
From commit to runtime
One path to production, for every integration.
- 01GitYour team pushes integration code to its own repository.
- 02BuildThe platform builds each commit, runs its tests and publishes one immutable image.
- 03PromoteThe same image moves from dev to test to prod. Production waits for an approval.
- 04RuntimeArgo CD rolls out the approved version; you see health and message flow.
Questions
Common questions.
Who owns the integration code?
You do. Integration code, repositories and their history stay yours. basis owns delivery, configuration, platform identities, operations and recovery.
Is relay a shared SaaS platform?
No. Each customer has its own installation, with separate runtime environments. Each integration runs in its own namespace, with its own database and broker identity.
Which runtimes does relay support?
Camel Quarkus and .NET. Both templates meet the same platform contract for health, metrics and message resend. Discuss your integration requirements with the team.
Bring us the systems you need to connect.
An engineer reads every enquiry and comes back to you about scope and service level.