EU Startups: news and funding

CIPHER Open Call 1: Up to €60,000 for Cybersecurity Startups and SMEs to Test an EU Cyber Range, Deadline 6 January 2027

Running a security operations team, a vulnerability scanner, an OT pentest practice or a NIS2 audit business? The EU-funded CIPHER project pays up to €60,000 per project, half of the costs, to companies that test, assess or extend its cybersecurity testing platform and cyber range. Its first open call is open to startups, SMEs, mid-caps, research organisations and universities, and a single company can apply alone. The deadline is 6 January 2027 at 17:00 CET. Before you apply, know the catch: you're paid to work on CIPHER's platform, and the results belong to CIPHER, not to you. Here's who qualifies, what each of the six challenges asks for and how to apply.
📌 Call card: CIPHER Open Call #1 (cybersecurity testing and cyber range)
Who can applyA single legal entity or a consortium of up to 3: startups, SMEs, mid-caps, research organisations and universities established in an EU Member State (including overseas countries and territories) or in Norway, Iceland or Liechtenstein. Non-public applicants must be EU-controlled and file a signed Ownership Control Declaration. One application per entity.
FundingUp to €60,000 per project, exactly 50% of the total eligible costs (the applicant co-finances the other 50%), paid as lump sums of 20%, 40% and 40% after each sprint. Indirect costs are a flat 7%. Subcontracting is not eligible.
Deadline6 January 2027, 17:00 CET (Brussels time)
StageProducts or solutions at TRL 6 to 8; a 9-month programme in three sprints, planned from April to December 2027
Apply viaF6S: application form, Technical Proposal (Annex 3, up to 12 pages for sections 1 to 5), budget workbook and the QES-signed Ownership Control Declaration (Annex 4), in English
Official call pageCIPHER Open Call #1

What CIPHER is, and what's new

CIPHER (Cybersecurity Intelligence, Protection and Holistic Enterprise Resilience) is a Digital Europe Programme project under grant agreement 101249732, with the European Cybersecurity Competence Centre (ECCC) as the granting authority. It is coordinated by EVIDEN Technologies in Romania, part of the Atos Group, and its 13 partners from 7 EU countries run from December 2025 to December 2028. The project is building a shared, "available-as-a-service" testing facility for critical infrastructure: automated penetration testing, an XDR platform, risk monitoring and a cyber range where attacks can be simulated safely, with a focus on operational technology (OT) in sectors such as energy, transport, healthcare and water.
The money reaches outside companies as cascade funding: CIPHER passes on part of its EU grant as small sub-grants, with a shorter application than a full EU proposal. The whole scheme is worth €4.32 million over the project. Open Call #1 opened on 26 October 2026 at 13:00 CET. Its own budget is not published, but the guide sets selection caps per challenge that add up to 25 to 35 places. A second open call will follow; Annex 2 says the "Development" work is deferred to it, but no dates have been published.
Three things to know before you start:
  • It's co-funding, not a full grant. The grant must be exactly 50% of your eligible costs. To get the full €60,000, you plan a project of about €120,000 and fund the other half yourself, usually through your team's time. Our guide to match funding requirements explains how companies cover their share.
  • CIPHER owns the results. Unless a challenge says otherwise, all outputs, deliverables and developments belong to CIPHER. You keep your background IP: the tools, know-how and assets you bring in. The exception is challenge R1, where a cyber range you contribute stays yours under a licence to CIPHER.
  • One grant per company, ever. No single legal entity may receive more than €60,000 in total from CIPHER's open calls, so winning the full amount now rules you out of more money in the second call.

Who can apply

Startups and micro-companies, SMEs, mid-caps, research and technology organisations and universities can all apply, either alone or in a micro-consortium of at most three independent legal entities. A consortium must include a Technology Provider (a startup, tech SME, research centre or university doing the technical work) and an End-User or Technology Adopter (an SME, infrastructure operator or association that validates the work in real settings), and may add a Certified Cybersecurity Auditor. If you're unsure which size category you fall into, see our guide to the SME definition in EU funding.
  • Countries: EU Member States, including overseas countries and territories, with a valid VAT number, and the EEA countries Norway, Iceland and Liechtenstein. No other countries are listed, so companies from the UK, Switzerland or Horizon Europe associated countries can't receive funding here.
  • EU control: under the security rules of the Digital Europe Regulation, every non-public applicant must be EU-controlled and submit the Ownership Control Declaration (Annex 4), signed with a qualified electronic signature (QES). CIPHER then checks it under its ownership and control procedure. A startup with a large non-EU investor holding veto rights should read this first, and the rule applies for the whole project.
  • Registrations: every applicant needs a valid VAT number and a PIC, the 9-digit Participant Identification Code from the EU Funding & Tenders Participant Register.
  • One application per entity. If you appear in two applications, alone or as a partner, only the first one submitted counts.

What it funds: six challenges

You pick exactly one challenge. Each one is a defined piece of work on CIPHER's platform, carried out with a CIPHER mentor, in sectors listed in Annexes I and II of the NIS2 Directive, with OT given priority. All active testing runs only inside CIPHER's isolated cyber range. Read the Technical Requirements (Annex 2) for each challenge's KPIs and limits: the consortium partners first run an in/out scope check, and a proposal that misses a baseline requirement is rejected before the experts see it.
ChallengeWhat you doWho it's for
K1: Regulatory capability gap assessmentMap CIPHER's toolset against NIS2 Article 21(2) and IEC 62443 and rate the gaps. Documentation only, no active testing.A certified auditor (for example ISO/IEC 27001 Lead Auditor or IEC 62443 assessor) with NIS2 critical-sector or OT experience
K2: Pentest methodology and gap assessmentWrite a best-practice OT pentest methodology and benchmark CIPHER's automated pentesting against it. Documentation only.OT or critical-infrastructure pentesters with credentials such as GICSP or OSCP
T1: Vulnerability management validationRun CIPHER's scanning toolchain end to end (SBOM, endpoint, network) inside the cyber range and validate the pipeline to Dependency-Track and DefectDojo.Vulnerability-management practitioners
T2: XDR onboarding and data-collection validationConnect your own environment (several OS types plus IDS/IPS or OT security appliances) to CIPHER's Wazuh-based XDR service and test detection.SOC and detection teams that control a representative environment
R1: Domain cyber-range contributionContribute a sector cyber range that measures NIS2 readiness, deployed into or federated with CIPHER. Capture-the-flag or training-only ranges are out of scope.Owners of an operational sector-emulation range (open source preferred)
P1: DevSecOps and platform automationWrite infrastructure as code, Helm charts and CI/CD pipelines for tools on a CIPHER list, delivered as pull requests to CIPHER's repositories.DevSecOps engineers (Terraform/OpenTofu/Ansible, Helm, CI/CD)
The guide sets how many applicants each challenge can take, to keep a balanced spread. The two testing challenges have the most room, with up to 10 places each; the auditor and cyber-range challenges have the fewest.
This is close to a paid validation contract: CIPHER defines the work and owns the outputs. It suits a company that wants hands-on access to an EU cyber range, references with critical-infrastructure operators and a seat at the Demo Day more than one that needs money to build its own product. For that, see our overview of cybersecurity innovation grants.

How much, and how you get paid

The grant is up to €60,000 per application, set at exactly 50% of the total eligible costs. Eligible costs are personnel, equipment, travel and other goods and services such as licences or events, plus a flat 7% for indirect costs. Subcontracting is not allowed. The budget goes into the CIPHER FSTP budget workbook, and the experts score how well the costs are justified.
  • Sprint 1 (month 1): onboarding and architecture report, then 20% (€12,000), which the guide treats as pre-financing.
  • Sprint 2 (months 2 to 5): technical work and a mid-term report, then 40% (€24,000).
  • Sprint 3 (months 6 to 9): full validation, a final report and a live Demo Day presentation, then the last 40% (€24,000).
Each payment follows an approved review, and you send the payment request within 5 working days of it. Because the grant is a lump sum, the guide says there will be no financial audits to check your costs; the reviews check the technical work. The Commission, OLAF and the European Court of Auditors can still check how the money was used, up to five years after the project. Selected teams also get a mentor, isolated test environments and scoped credentials, access to CIPHER's XDR service, WORM storage and risk-monitoring tools, and promotion by the project.

How to apply before 6 January

  1. Choose your challenge and check its baseline requirements in Annex 2: certifications for K1 and K2, a representative environment for T2, an operational range for R1.
  2. Check your ownership. Prepare the Ownership Control Declaration and get a qualified electronic signature (QES) in time; a scanned signature is not enough.
  3. Write the Technical Proposal on the Annex 3 template, in English: up to 12 pages for sections 1 to 5. A proposal over the limit can be disqualified.
  4. Fill in the budget workbook so that the grant is exactly 50% of the costs and no more than €60,000.
  5. Submit on F6S (f6s.com/cipher-opencall1) as PDFs, with the project acronym in each file name. Resubmission is only guaranteed if you ask support@f6s.com at least 2 business days before the deadline.
Experts score each proposal on four criteria: excellence (30%), relevance to CIPHER (30%), impact and scalability (20%) and quality of implementation (20%). Each criterion needs at least 3 out of 5, and the total at least 10 out of 15. The top-ranked applicants get an online interview. If you're rejected, you can appeal within three working days. The full rules are in the Guide for Applicants.
StepTiming in the guide
Applications open26 October 2026, 13:00 CET
Info webinar10 December 2026 (time not yet published)
Submission deadline6 January 2027, 17:00 CET (Brussels time)
Eligibility and technical check13 to 23 January 2027
Expert evaluation and online interviews24 January to 13 February 2027
Results letter to all applicants17 March 2027
ContractingDocuments normally within about two weeks
Sprint 1, Sprint 2, Sprint 3April to May, June to September, October to December 2027
Also working on cybersecurity compliance? The SECURE open call pays single SMEs up to €30,000 towards Cyber Resilience Act preparation until 11 December 2026. If your security tool is open source, NLnet's Restack and CodeSupply grants pay €5,000 to €50,000 with no co-funding asked, paid per milestone, until 3 January 2027.
Never miss a deadline

CIPHER Open Call #1 and dozens of other EU and national deadlines are in our grant deadlines calendar.

FAQ: CIPHER Open Call #1

When is the deadline?

6 January 2027 at 17:00 CET (Brussels time). Applications go through F6S only; there is a single closing date and no late or emailed submissions.

How much funding can a startup get?

Up to €60,000 per project, which must be exactly 50% of the eligible costs, so a full grant means a project of about €120,000. It is paid in three lump sums of 20%, 40% and 40%.

Can a startup apply alone?

Yes. A single legal entity in the EU or in Norway, Iceland or Liechtenstein can apply alone. Consortia of up to three are also possible and must include a technology provider and an end user.

Who owns the results?

CIPHER owns the outputs of the funded challenges. You keep your pre-existing IP. For challenge R1, a cyber range you contribute stays yours under a licence to CIPHER.

Can companies with non-EU investors apply?

Only if the company is EU-controlled. Every non-public applicant submits a QES-signed Ownership Control Declaration, and CIPHER assesses it. The condition must hold for the whole project.

When are the results, and when does the work start?

Results are planned for 17 March 2027, with the 9-month programme running from April to December 2027. The call says these dates may change.
2026-10-29 07:15 Funding calls