About
Budapest-based technology partner for SAP/ERP, web, AI and mobile projects
Corevanix Kft. delivers enterprise system integration, web development, AI automation and mobile app development for companies in Hungary and the EU. We work with a fixed scope, milestones and written handover — inside the client’s own environment, under the client’s rules.
- Registered office: Budapest, Hungary
- Working languages: Hungarian and English
- Clients: SMB and enterprise customers in Hungary and the EU
- Four areas: SAP/ERP, web development, AI automation, mobile apps
How we work
Four rules that apply to every project
Not promises but operating terms. The same ones appear in the contract.
Specialised partner network
We staff projects with proven partners specialised by field: SAP consultant, frontend, mobile, data and AI engineers matched to the task. Every party we bring in works under a non-disclosure agreement (NDA) and under the client’s rules.
Fixed scope, on time
Scope is written down and split into milestones. Every milestone is a tested, acceptable state. What we commit to, we deliver on schedule; if a risk threatens the deadline, we flag it the day it appears, not before handover.
In your environment
For SAP/ERP work and every other project, we work inside the client’s own systems: your repository, your developer access, your infrastructure. We do not export data and we do not run a parallel copy on our own machines.
Handover and full ownership
Delivered source code, documentation and configuration belong 100% to the client. At project close we produce a written handover, revoke our access and keep no copy.
Our data principles
The client’s data belongs to the client
Six points we follow on every project, regardless of size.
We keep no code
Finished source code lives in the client’s repository. After project close we keep no clone, branch or build artefact.
We store no data
Production or test data never leaves the client’s systems. When development needs data, we use it inside the client’s environment, anonymised.
NDA for every party involved
Every partner and subcontractor signs a non-disclosure agreement before work starts, matching or exceeding the client’s own NDA.
Access revoked at project end
On handover day we return our developer, admin and VPN access, and record this in the handover report.
Everything stays in the client’s systems
Code, documentation, configuration, tickets and the decision log live in the client’s tools (repository, wiki, ticketing), not ours.
Documented on audit request
If the client’s internal audit or an authority asks, we confirm in writing which data we accessed, for how long, and when access was revoked.
What to expect from a project
Four steps from discovery to support
- 01
Discovery
A 30-minute call, then a 1-2 week assessment of the existing systems. Output: a written situation report and the candidate solutions with their risks.
- 02
Scope and proposal
Fixed scope, milestones, deadlines and price in writing. What is not in the scope is not in the project — changes are handled separately, in writing.
- 03
Delivery by milestones
Fortnightly demo inside the client’s environment. Every milestone is a tested, documented state that can be accepted on its own.
- 04
Handover and support
Written handover, documentation, access revocation. Then a support period as agreed — code and data stay with the client throughout.
What we don’t do
Four things we don’t take on
Template work below cost
If a task can be solved with a template, we say so and don’t rebuild it at a higher price. If it needs custom development, we won’t do it at template pricing, because quality and the deadline would suffer.
Keeping client data
Not as a reference and not for “later reuse”. After project close, no client code, data or document remains with us.
Promises we can’t measure
Every commitment comes with a metric and a way to measure it: response time, error rate, load time, documents processed per hour. What can’t be measured doesn’t go into the contract.
Development in our own sandbox with your data
Development and testing happen in the client’s environment. If that is not possible, we say so up front and decide on the alternative together.
Let’s talk about your project
After a 30-minute call you’ll know whether it’s worth moving forward: a concrete scope outline, the risks and a realistic estimate.