Partnerships · Research & Development

A production platform,
offered as project infrastructure.

Enoqi is a decarbonisation management platform in live operation across European value chains. We join research and innovation consortia as a technology partner — bringing a working platform, full intellectual property control, and a route from project results to the market.

Start a conversation Download the platform overview →
Legal entity ENOQI j.s.a.
Bratislava, Slovakia
Ownership & control 100 % EU-owned
and EU-controlled
Country status Horizon Europe
widening country
Platform status In production
live customer tenants
Technology readiness Feature pipeline
spanning TRL 1–8
IP position Product fully owned
no third-party licences
Programme experience Team track record from tens of projects — Digital Europe · Horizon Europe · Erasmus+ · CEF Telecom
what we bring

Not a subcontractor. A partner that owns what it builds.

Consortia do not need another subcontractor. They need partners who own what they build, move at research speed, and can carry results past the final review. Enoqi is structured for that role.

01

Full ownership, purpose-built project versions

The Enoqi platform is developed and owned entirely in-house — codebase, data model, and methodology. There is no upstream vendor whose roadmap constrains what a project can do with it. For research work, we spawn dedicated project instances: isolated environments derived from the production platform, free to diverge — experimental data models, modified scoring logic, novel interfaces — without touching production tenants. What a project needs to exist can be built, because nobody else’s permission is required.

02

Modern engineering, appetite for the unproven

The platform already runs LLM-assisted document ingestion, AI-supported emission-source mapping, and a formally specified ecosystem ontology governing its data model. Our development practice is specification-driven and heavily automated, and we treat new techniques as material to work with rather than risk to avoid. A research project that wants to test an approach nobody has productised yet finds a partner who considers that the interesting part.

03

A team that has done this before

Enoqi’s team members carry experience from tens of EU-funded projects, principally under Digital Europe, Horizon Europe, Erasmus+, and CEF Telecom — a track record built as individuals across earlier roles, now concentrated in one company. We know the machinery: proposal logic, consortium agreements, deliverable discipline, reporting cadence, and the difference between a work plan that reads well and one that survives month eighteen. A consortium taking Enoqi on board does not spend the first reporting period teaching its technology partner how a project runs.

04

A live testbed, not a promised prototype

Most project plans budget significant effort for building a demonstrator. Enoqi arrives with one running: a production platform with real organisations, real supply-chain relationships, and real emission data flows. Pilots start on live infrastructure from month one, and validation happens in an operational environment rather than a laboratory mock-up.

05

A credible exploitation path

Project results rarely survive the final review; ours have somewhere to go. Enoqi is a commercial SaaS company with a defined market, a pricing model, and a customer pipeline. A method, dataset, or component developed in a project can transfer into the production platform and reach paying users — which is the exploitation story evaluators ask for and consortia struggle to supply.

project instances

The production platform is the trunk.

Each research engagement receives its own instance — a fork of the platform with its own data space, its own experimental modules, and its own release cadence, governed by the project rather than by our commercial roadmap.

Instances can integrate external components, expose research APIs, or run modified methodology under controlled conditions. What proves out can be merged back toward production; what does not is contained, documented, and retired.

The consortium gets a real system it can shape; the production platform and its customers stay protected.

Production platform and project instances A vertical trunk labelled production platform, with three project instances branching off to the right: an experimental data model, modified scoring, and an external integration. One instance returns validated results to the trunk; another terminates as documented and retired. PRODUCTION PLATFORM PROJECT INSTANCE Experimental data model PROJECT INSTANCE Modified scoring logic PROJECT INSTANCE External integration validated results documented & retired
Instances are isolated from production by design. The merge route back to the trunk is the exploitation mechanism — and the route is optional, not automatic.

Isolated by design

Separate infrastructure, data, and access control per project instance.

Free to diverge

Experimental schema, scoring, and interface changes without production constraints.

A path back

Validated results have a defined merge route into the commercial platform.

Not one point on the readiness scale — a pipeline.

Core modules — calculation, supply-chain data exchange, AI-assisted import — run in production with pilot customers. Behind them, features at every stage of maturity move through the same pipeline: concepts under formal specification, capabilities in validation, releases hardening toward production. A research project enters this pipeline at whatever stage fits its ambition — an early-stage concept gets an instance to prove itself in; a validated method gets the merge route to operational use. The pipeline is the exploitation mechanism, not a metaphor for it.

Enoqi feature pipeline across technology readiness levels A band running from TRL 1 to TRL 9 in three zones: research frontier (1 to 4), validation (5 to 7), and production (8 to 9). Feature markers sit at TRL 2, 4, 6 and 8; TRL 9 is deliberately empty. A bracket spanning TRL 2 to 7 marks where project instances operate, and an arrow marks the merge route into production. project instances operate here AI emission-source mapping calculation · data exchange · AI import TRL 8 — reached concepts in specification supply-chain data exchange 123 456 789 merge to production not claimed RESEARCH FRONTIER VALIDATION PRODUCTION
TRL 9 is left empty on purpose. The scale runs to 9; our furthest feature has reached 8, and we say so.
roles

How we fit a consortium.

We fit consortia in several configurations, alone or combined.

Technology partner

Platform development, integration work, and technical work-package delivery.

Pilot infrastructure provider

Project instances of the platform as the demonstration and validation environment.

SME engagement partner

Recruiting and onboarding SME participants through the platform’s supplier-hub mechanism.

Methodology contributor

Carbon accounting, supply-chain data exchange, and decarbonisation-posture assessment expertise into research design.

Exploitation partner

Carrying project results into a commercial product with an existing route to market.

Roles combine. Most consortia take us on as a technology partner and pilot infrastructure provider together, with the exploitation role following from the same platform.

Partnering · open to calls

Building a consortium?

Tell us about the call and the gap you are trying to fill. We respond with a concrete statement of what Enoqi would contribute — usually within a week.

Partner search profiles available on request for the Funding & Tenders Portal and national NCP databases.

Tell us about the call → Download the platform overview

Or write to us directly.

A call reference, a draft concept note, or a question about whether the platform fits your work plan — a real person replies. No sales sequence.

  • Response Within 1 business day · Mon–Fri, 9:00–17:00 CET
  • Email
  • Where ENOQI j.s.a. · Bratislava, Slovakia
Open the partnering form