Programs

Two tracks: four product areas where our technology stack creates civilian and humanitarian value, and social programmes where help reaches people directly.

How we choose what to work on

We work along two tracks, and the selection criteria differ. In the product track we are not tied to a single technology: teams take on problems where they can create real civilian and humanitarian value, and where Ukrainian solutions either do not exist at all or are priced out of reach. In the social track we look at something else — whether there are people who lack access to help, and whether we can provide that access.

The four areas below are listed in order of priority, set by the scale of the need, the availability of donor funding, and how far the market is already covered.

All directions follow from clause 3.2 of the Statute. Activities requiring licences or permits are carried out only once those are obtained — clause 3.3.

Priority 1. GreenTech — environmental monitoring

Satellite and AI monitoring of the consequences of the war: the condition of forests, water and soil. Plus tools for smart energy grids.

Why first. Assessing wartime environmental damage is its own category of international funding. The European Green Deal and the LIFE programme explicitly allocate money for such data. Meanwhile Ukraine lacks the measurement instruments: damage is estimated rather than observed.

What we build

  • Satellite imagery processing to detect changes in forest cover and contamination
  • Open datasets and maps for municipalities and researchers
  • Load forecasting tools for local energy grids

Who needs it

Municipalities, to record damage and qualify for recovery funding. Researchers, to have continuous observation series. Donors, to see where green recovery money goes.

Priority 2. GovTech — the state and municipalities

Local digital services, open data and geographic information systems for municipalities. Transparent reconstruction dashboards built on DREAM data.

Why second. Working through DREAM became mandatory for reconstruction projects in 2026, yet most municipalities have no in-house IT capacity to meet that requirement. The gap between the requirement and the capability is our problem to solve.

What we build

  • Dashboards showing the status of reconstruction projects to a municipality and its residents
  • Geographic information tools for tracking municipal infrastructure
  • Publication of open data in machine-readable formats

Priority 3. HealthTech and AssistiveTech

Health, rehabilitation and accessibility: telerehabilitation, digital mental health, prosthetic control, AI assistants and navigation for people with disabilities.

Why third. The need is measured in millions of people and it is growing, yet almost nobody works here with deep technology — the market is seen as difficult and slow. The area maps onto Ukraine's National Barrier-Free Strategy.

What we build

  • Telerehabilitation: sessions at home supervised by a specialist
  • Digital tools supporting mental health
  • Prosthetic control interfaces and assistive navigation applications

Priority 4. ReconstructionTech and BuildTech

Damage assessment based on satellite data and machine learning, digital twins of municipalities, energy efficiency tools.

Why fourth. The scale of the need runs into hundreds of billions of dollars, but this is the most competitive area: large contractors already operate here. We enter where speed and cheapness of measurement matter, not construction capacity.

What we build

  • Automated damage assessment from imagery
  • Digital twins of municipalities for reconstruction planning
  • Tools for calculating building energy efficiency

Social programmes

The organizationʼs second track. A product can be handed to a client and left behind — a social programme cannot. There is no app that settles it: there is a person with a need and a professional who can help. Our job is to make that meeting possible.

Such programmes are provided for directly by clause 3.2.14 of the Statute — social, educational and humanitarian programmes — as well as clauses 3.2.4 and 3.2.7. The same rule applies as to everything else: activities requiring a licence or permit are carried out only once it has been obtained (clause 3.3).

Running now. The first activity of the social track is already live — the anonymous veterans needs survey, open since 10 August 2026. Its results will shape the first support programme and will be published openly.

Direct help for people

Access to qualified help for people for whom it is otherwise too expensive or too far away. A programme in this area is being prepared for launch.

Non-formal education

Training for care professionals and for people going through a difficult period. Certificates are ours, not state-recognised — clause 3.2.7.

Evidence on what works

Every programme collects anonymised outcome data. Without it there is no way to tell help from the appearance of help — or to report honestly to a donor.

Both tracks run on the same logic: technology provides leverage where it is missing, and programmes provide it where the lever is a person. Sometimes the two meet in one problem, and then the product becomes an instrument of the programme.

The mission running through both tracks

Veteran reintegration

Not courses but real roles: product managers, developers, analysts, testers and subject-matter experts on the teams building the products above.

A door for beginners

A first genuine experience on a team even without a portfolio — mentored by seniors, on projects worth showing.

European integration

Our products close specific state needs, including within negotiation Cluster 6: export control and external relations.

How work on a project is organized

  1. The need. A real problem from a municipality, an institution or a public body. We record who lives with it and what changes if it is solved.
  2. The team. A veteran or subject-matter expert, students, a mentor. Before work starts, a contract assigning intellectual property rights is signed.
  3. The prototype. Development mentored by practitioners from industry. The mentor reviews code and decisions rather than delivering lectures.
  4. The test. Verification in real conditions with whoever posed the problem. Metrics are fixed at the start, not fitted to the result.
  5. Scale. Deployment, or spin-off through licensing — without the organisation taking equity.

A project counts as done when somebody uses it. Not when the pitch is ready and not when the report is filed.

Frequently asked questions

01

How is a direction chosen for a new project?

By three criteria: the scale of the need, the availability of donor funding for that theme, and how far the market is already covered by other players. Priorities are reviewed annually by the Meeting.

02

Do you work with dual-use technology?

Clause 3.2.1 of the Statute allows it, but clause 3.3 gates such work behind state export-control authorisations. We begin only once those are obtained. The main focus is civilian and humanitarian applications.

03

Who owns the results?

Intellectual property rights vest in the organisation under section 8 of the Statute. A contract assigning those rights is signed before work begins, and specific results are recorded in handover acts.

04

What happens to a successful product?

It spins off into an independent venture through licensing. The organisation takes no equity — it only licenses the technology at market terms. Royalties flow back into statutory activity.

05

How long does one project take?

From need to a validated prototype, roughly three to six months depending on complexity. Deployment and scaling are a separate stage with their own budget.

Ready to take part?

Take a role on a team or bring a problem that needs solving. We reply within five working days.