01
Offensive Security
Red teaming and adversary simulations that test people, processes, and technology against realistic attack paths.
- Red-team operations
- Adversary simulation
- Detection-focused debriefs
- Authorized malware and ransomware simulation
OFFENSIVE SECURITY · AI SYSTEMS · SWITZERLAND
Safematix delivers hands-on offensive security, ethical hacking, AI security, and AI engineering for organizations that need evidence—not theatre.
Based in Wollerau, SwitzerlandWorldwide remote & on-siteBackground-check ready
01 / Services
01
Red teaming and adversary simulations that test people, processes, and technology against realistic attack paths.
02
Authorized, clearly scoped penetration testing that turns exploitable weaknesses into prioritized fixes.
03
Attack the model, agent, and tool chain before someone else does. Find practical attack paths and help harden the controls around them.
04
Build local inference, RAG, and agent systems for high-security environments—from model training and tuning to production operations.
05
Strategy, architecture, governance, and resilience for regulated and high-security environments.
06
Two days of practical secure design, coding, review, and testing for engineering teams.
02 / PACKAGES
Fixed-scope starting points for security, regulated AI adoption, and measurable automation. Choose a package or bring a different scope.
For organizations of different sizes and industries. Robert brings experience from pharma, banking, insurance, telecom, industry, OT, and nuclear power plants.
START WITH CLARITY
CHF 3’900
2 working days
Prioritize security risks and AI opportunities before committing to a larger assessment or build.
AUTHORIZED TESTING
CHF 9’800
5 working days
Find exploitable weaknesses in one web application and turn them into prioritized, reproducible remediation.
AGENT & TOOL-CHAIN DEFENSE
CHF 14’800
8 working days
Attack one agent and its tool chain, then help harden the controls that contain real attack paths.
AUTOMATION WITH CONTROL
CHF 24’800
12 working days
Turn one costly workflow into a secure, evaluated agent pilot—with controls and measurable operating assumptions, not automation theatre.
Flexible engagements: CHF 2’200 per working day. Longer, clearly scoped remote projects: CHF 2’000–2’100. Short-notice OT, red-team, and high-security engagements: CHF 2’400–2’600, subject to scope.
All package prices and day rates exclude applicable VAT and pre-approved travel and third-party costs, unless expressly included in the order form. Fixed-price packages apply within their stated scope. Scope, authorization, and start date are confirmed in writing before work begins. Regulatory mapping is technical, not legal advice. Savings and compliance outcomes are not guaranteed.
03 / Approach
A clear process before, during, and after the technical work. You always know what is in scope, what happens next, and which artifact you receive. Phases and deliverables depend on the selected package and written scope. Assessments recommend and verify client fixes; hands-on remediation or pilot implementation is included only when expressly scoped.
Clarify objectives, systems, data classification, constraints, and the result your team needs. A short confidential scoping call becomes a written target list, success criteria, and fixed or separately agreed scope. The price basis is agreed separately.
Your responsibility Name a technical contact and describe the business objective. No secrets or sensitive exploit details in the first enquiry.
Before testing, the system owner approves targets, roles, timing, evidence handling, and stop conditions. Communication, access, and escalation paths are agreed explicitly.
Your responsibility Confirm ownership and provide agreed accounts, roles, and environment access.
Test manually, research, or build hands-on. Work is limited to the agreed scope, with short checkpoints and no black-box handoff. AI-assisted work is verified by Robert before it becomes evidence.
Your responsibility Answer technical questions and flag operational constraints early.
Findings and design decisions are explained in business and technical terms. Each item includes preconditions, reproducible evidence, impact, root cause, and a prioritized fix—without inflated severity.
Your responsibility Bring the people who can assess impact and implement fixes.
Review remediation and control changes together, then repeat the relevant test or evaluation. Results distinguish fixed, partially fixed, and open items, including residual risk.
Your responsibility Apply agreed fixes and provide the updated build or configuration for verification.
Finish with an operating guide, knowledge transfer, and next-step decisions. Engagement material is handled through the agreed secure process; ongoing support is a separate, explicit scope.
Your responsibility Confirm owners for remaining actions and operating responsibilities.
One direct technical contact throughout. No black box, no junior handoff, and no sensitive details in the initial form.
04 / PROOF
Public disclosure of a critical WordPress Core vulnerability, grounded in reproducible technical research.
MCP runtime policy and audit controls with mcp-firewall, plus pre-deployment scanning with mcpwn.
Published work on model behavior, quantization, and deployable formats.

05 / About
Robert Ressl
Safematix is founded and led by Robert Ressl, a Swiss security and AI systems engineer. His work spans Linux and cloud platforms, global offensive-security delivery, model engineering, and regulated production. You work directly with the person doing the technical work.
Available for deep background checks and work in high-security environments.
Remote worldwide. Travel for on-site engagements by arrangement.
06 / FAQ
In Wollerau, Schwyz, Switzerland, with delivery worldwide.
Both. Remote delivery is available worldwide, with travel for on-site needs by arrangement.
Yes, and I can work in high-security environments.
Yes. Safematix combines offensive security and ethical hacking with model, agent, MCP, and inference expertise.
You receive a direct reply to arrange a confidential scoping conversation. Do not send secrets or sensitive exploit details through the initial form.
07 / Contact
Tell me what you need to test, secure, or build. No sensitive details at this stage.