LIMITED B2B PILOT
Apply for the PAXECT Readiness B2B Pilot
PAXECT is inviting EU manufacturers, importers and connected-product teams to apply for a controlled pilot focused on practical CRA-readiness evidence.
Applications are open for selected companies. Each request is reviewed manually based on product fit, technical scope, readiness needs and available pilot capacity.
A managed PAXECT Readiness Scanner Box, protected transfer to the Cloud Workspace, Readiness Reports, evidence follow-up and Remediation Guidance — built for companies without a large product-security team.
Guided pilot onboarding. Managed Scanner Box. Structured Cloud Workspace review.
Limited pilot. Defined scope. No public checkout. No automatic fixing.
B2B pilot eligibility
PAXECT Readiness is currently available through a limited pilot for EU manufacturers, importers and connected-product teams.
The pilot is intended for organisations working with connected products. It is not a consumer product, hobby scanner or general IT scanning service.
Applications are reviewed manually. We may request company details, product information, technical context and the intended use before confirming participation and a defined pilot scope.
Participation, timing, responsibilities and applicable terms are agreed before onboarding.
CRA implementation is underway. Product teams need practical evidence.
The Cyber Resilience Act is already in force. Reporting obligations start from 11 September 2026, and the main CRA obligations apply from 11 December 2027.
For many smaller manufacturers and importers, the challenge is practical:
- no dedicated product-security team
- no time for complex enterprise implementation
- limited budget
- firmware and device evidence scattered across suppliers
A report alone is not enough.
Companies need to prove what is inside a product and show what happens after a finding is discovered: follow-up, validation and audit.
PAXECT Readiness: box-first CRA-readiness for connected devices.
PAXECT combines the PAXECT Readiness Scanner Box with protected transfer to a customer Cloud Workspace.
During pilot onboarding, the Scanner Box is set up for an agreed product scope and used to collect technical evidence from supported connected devices or firmware.
Customers do not need Linux knowledge, security tooling experience or a dedicated product-security team to get started.
Live device scan
For Linux-based devices available on the local network.
Firmware image analysis
For firmware files, even when no active device is available.
From product evidence to customer-controlled follow-up
A Readiness Report and Evidence Dossier make findings, available evidence and evidence gaps reviewable. Your organisation decides whether supplier information, Remediation Guidance or another approved follow-up is needed.
Any fixing is a separate, optional route. It begins only after explicit customer approval, defined scope, review and validation.
Current product route
What you get
Scanner Box, protected transfer, Cloud Workspace, Readiness Reports, Evidence Dossier, Supplier Requests and Remediation Guidance.
PAXECT Readiness Scanner Box
A managed local appliance for collecting technical evidence from supported connected devices and firmware within an agreed pilot scope.
Protected transfer
Collected product evidence moves through a protected route from the Scanner Box to the customer Cloud Workspace. The Scanner Box does not store customer reports.
Cloud Workspace
A customer-specific environment for storing and reviewing reports, evidence records, product context, evidence gaps and follow-up needs. Report and evidence data are protected with encryption during transfer and storage.
Readiness Reports and Evidence Dossier
Structured findings and traceability context support internal review without claiming certification or guaranteed compliance.
Supplier Requests
Missing supplier information can be recorded and routed into a structured evidence follow-up process.
Remediation Guidance
Advisory guidance translates findings into clearer next steps. PAXECT does not automatically modify products, firmware or software.
Customer control and record ownership
Your organisation retains control of its reports, evidence, workspace decisions and follow-up records.
Any separate fixing route is optional and starts only after explicit customer approval, defined scope, review and validation.
How the B2B pilot works
Three practical steps from pilot onboarding to controlled follow-up.
Set up your Scanner Box
During pilot onboarding, your organisation receives the PAXECT Readiness Scanner Box and sets it up within the agreed technical environment.
Collect product evidence
Use supported live-device scanning or firmware image analysis to collect technical evidence within the agreed pilot scope.
Review and follow up
Review Readiness Reports, the Evidence Dossier and evidence gaps in the Cloud Workspace. Your team decides whether supplier follow-up, Remediation Guidance or another approved next step is needed.
Built for practical B2B CRA-readiness
PAXECT is designed for connected-product teams that need clearer evidence, structured review and customer-controlled follow-up without unnecessary complexity.
| Business context | PAXECT B2B pilot approach |
|---|---|
| Smaller connected-product teams | A manageable evidence workflow without requiring a large internal product-security team. |
| Larger organisations and product teams | Structured evidence, reports and follow-up that can support work across products and suppliers. |
| Pilot onboarding | A managed Scanner Box with guided setup within the agreed technical environment. |
| Product evidence | Supported live-device scanning and firmware image analysis within the defined pilot scope. |
| Reviewable output | Readiness Reports and an Evidence Dossier with product and traceability context. |
| Missing supplier information | Supplier Requests support structured evidence follow-up. |
| Findings that need next steps | Remediation Guidance supports customer-controlled review and decisions. |
| Defined B2B engagement | Scope, responsibilities, timing and applicable terms are agreed before onboarding. |
Current support and roadmap
The current pilot scope combines Linux-based device and firmware evidence with protected transfer, Cloud Workspace review, Readiness Reports, evidence follow-up and Remediation Guidance. Android APK scanning has been tested as an expansion track. Windows, iOS and broader Cloud/API readiness checks remain roadmap items.
| Area | Status |
|---|---|
| Linux live device evidence | Pilot scope |
| Linux firmware image analysis | Pilot scope |
| SBOM/component insight | Pilot scope |
| Protected evidence transfer | Pilot scope |
| Cloud Workspace review | Pilot scope |
| Readiness Reports and Evidence Dossier | Pilot scope |
| Supplier evidence follow-up | Pilot scope |
| Remediation Guidance | Pilot scope |
| Android APK scanning | Tested expansion |
| Windows EXE/MSI scanning | Roadmap |
| iOS IPA scanning | Roadmap |
| Cloud/API readiness checks | Roadmap |
Remediation Guidance is advisory. PAXECT does not automatically modify products, firmware or software. Any fixing requires explicit customer approval, defined scope, review and validation.
Explore PAXECT Readiness
Review the PAXECT workflow, evidence approach and practical CRA-readiness guidance for connected-product teams.
Website pages
Knowledge Hub articles
EU funding context
European programmes such as SECURE have supported small and medium-sized enterprises working on cyber resilience and CRA preparation. The first SECURE open call listed a €5 million budget, grants of up to €30,000 and a 50% co-financing model. That call closed on 29 March 2026.
Where a current funding programme permits, PAXECT Readiness may be relevant to projects involving product evidence, reporting and controlled follow-up. PAXECT does not determine funding eligibility or guarantee funding.
Always check the current programme status, scope and eligibility requirements. See the official SECURE programme information.
Apply for the B2B Pilot
This form is for B2B pilot applications only. It is not a public checkout or product purchase.
Use this form to apply for the limited pilot and let us review your organisation, product type and CRA-readiness needs.
PAXECT uses your information to review your pilot application and contact you about PAXECT Readiness. We do not sell your data.
If the form does not load, open the B2B pilot application form in a new tab.
What happens after you apply?
After your request, we follow a simple B2B intake process.
Review
We review your company and use case.
Fit check
We check whether PAXECT Readiness fits your product type.
Next step
If there is a match, we may invite you to discuss a defined pilot scope and the next review step.
Pilot onboarding begins only after scope, responsibilities, timing and applicable terms are agreed. Applying does not create a purchase obligation or guarantee acceptance.
FAQ
Short answers for common business questions.
Is PAXECT Readiness for consumers?
No. PAXECT Readiness is currently offered through a limited B2B pilot for organisations that manufacture, import, distribute or manage connected products in the EU market. Applications are reviewed manually, and business verification may be required.
When do CRA obligations start?
Reporting obligations for actively exploited vulnerabilities and severe incidents start from 11 September 2026. The main CRA obligations apply from 11 December 2027.
Does PAXECT make my product CRA compliant?
No. PAXECT supports CRA-readiness evidence and controlled follow-up. It does not certify compliance, provide legal advice or guarantee that a product or organisation is compliant.
Do I need a large security team to use PAXECT?
Not necessarily. PAXECT is designed to make evidence collection and review more manageable for smaller connected-product teams. Your organisation still remains responsible for its decisions and for involving appropriate technical, legal or compliance expertise where needed.
How is the Scanner Box set up?
Pilot onboarding includes guided setup of the PAXECT Readiness Scanner Box within the agreed technical environment. The customer does not need to build or manage the underlying scanner environment.
Can I review information from a tablet or laptop?
Yes. Reports and evidence records can be reviewed through a supported web browser on a tablet or laptop. They are stored in the customer-specific Cloud Workspace and protected with encryption during transfer and storage. Product evidence is collected through the PAXECT Readiness Scanner Box, which does not store customer reports.
Can reports be stored locally?
No. Reports are stored in the customer-specific Cloud Workspace. PAXECT does not provide a product function for creating or exporting local or offline report copies. Handling outside the PAXECT environment is outside the supported product scope and remains the customer’s responsibility.
Is PAXECT only a scanner?
No. PAXECT combines the Scanner Box with protected transfer, a Cloud Workspace, Readiness Reports, an Evidence Dossier, Supplier Requests and Remediation Guidance. Your organisation decides the follow-up. Any fixing is separate and requires explicit approval, defined scope, review and validation.
About PAXECT
PAXECT is a Netherlands-based startup building practical CRA-readiness infrastructure for European manufacturers and importers of connected devices.
We focus on companies that need technical evidence, reviewable reports and a controlled improvement path, but do not have a large product-security team or months for complex enterprise tooling.
Built in the Netherlands. Focused on the EU market. Designed for B2B.
CRA-readiness should not require an enterprise security team.
Start with technical evidence, reviewable reports and a controlled route from findings to improvement.