The Onveda Lab: Lower the Risk Before You Adopt New Tech
In our lab we test new technology before it goes into a client project. What we care about is whether it runs reliably. Whether it is trending does not count.
Every test produces an assessment, an architecture proposal and a guide for putting it to use. That way, new technology is not a gamble for you.
Test new technology first, then put it into production
Not every new technology is ready for production. In the Onveda Lab in Langenfeld we try out what works. We do that before a client system depends on it.
- Criteriaset before the test
- Lab testbefore a client system depends on it
- Assessmentyes or no
- Architecture proposal
- Deployment guide
Criteria are set before the test
Before every test we write down what we are checking and which result means we adopt or drop the technology. The outcome is a yes or a no.
Security from the start
We check data protection, access control and logging as part of every test. A technology that fails here does not go into any project.
Production standards
Automated tests, monitoring and a rollout that can be reversed. Only what meets these three goes into production.
What we are working on in the lab
Five topics in the lab
AI integration
We check where AI takes work off people and where it stays a toy. That includes rules for its use, review of its results and data protection.
Reliability and monitoring
Your system has to be available when customers need it. We test monitoring, error handling and emergency plans before a real incident tests them.
Integration between systems
Once systems talk to each other, things get complicated. We test API patterns, rules and versioning, for example for connecting to SAP S/4HANA. That keeps an integration from becoming a permanent construction site.
Performance under load
An application has to stay fast under load. We test with load profiles, caching and scaling on Kubernetes. A catalog with more than 5 million items, like the one at LANXESS, does not forgive a slow search.
Security from the start
Adding security after the fact is expensive and error-prone. We plan it into the architecture from day one. That is where it belongs.
Rules and templates you can reuse
The lab produces patterns, guidelines and templates. They apply to the next project just as much as to the one after.
Playbooks and patterns
Tested guides for integration, deployment and incident handling. Your team looks things up instead of starting from scratch every time.
Production checklists
The checklist states what has to be in place before anything goes live. If an item is open, the release moves. Then nobody heads into the weekend nervous on a Friday.
Infrastructure starter kits
Templates for the pipeline, monitoring and the Kubernetes environment. A new project starts with a working foundation, not from zero.
Risk management
A fixed procedure: collect risks, rate them by impact and likelihood, assign measures. It replaces the crisis meeting that only happens after the incident.
You are modernizing or planning to add AI
Then it pays to look at the risks before you start. Our Software Audit takes two weeks and costs €3,000 to €6,000 at a fixed price. The intro call before it takes 30 minutes and is free. After the audit you know three things.
- Which systems you need to connect
- Where the risks are
- Which steps are due in the next 90 days
Jens Bohl Founder and Managing Director