Design partner program
For agencies, freelancers and hosts who are responsible for many PHP or WordPress sites they didn't write — and get the call when one of them is hacked.
The deal
You get
- phpwarden Pro, free for six months — the fleet dashboard across all your sites, the maintained feed rebuilt twice a day, a weekly live check of each site from outside, "fixed and verified" after each re-check, and an alert when something you already run starts being exploited.
- A direct line to the maintainer. Your bug reports and feature asks go to the person who writes the code, same day.
- A real say in what gets built next, especially the fleet features.
- Locked-in pricing at the end if you stay, at whatever it costs then minus a founding discount.
We ask
- A short email every two weeks — what was useful, what was noise, what you'd pay for.
- Honest feedback, including "this is wrong" and "I'd never use that."
- If, and only if, it earns it: one quotable sentence and permission to name you as a user.
- Nothing else. No commitment to pay, no lock-in. Leave whenever.
Is this you?
- You maintain 10 or more PHP, WordPress or Laravel sites for clients, or host them.
- "Which of these actually needs patching today?" is a question you answer by feel, or by reading every advisory.
- You've been burned by a scanner that cried wolf on 400 "criticals" — or stayed quiet on the one that mattered.
- You'd like a report you can forward to a client that says what's exposed and what isn't, ranked by real risk.
If you're a solo developer with one or two projects, you don't need this — the free CLI does everything for you and always will.
Apply in one email. Tell me roughly how many sites, what stack (WordPress / Laravel / mixed), and the one patching question you wish you could answer faster.
Apply — [email protected]You'll get a reply from Oroma, not a form. Usually within a day.
Hosts, control panels and maintenance platforms
If your customers run many PHP sites, phpwarden is a channel fit rather than a single account: every site reports in with one line, the fleet view ranks them by what is actually being exploited, and the exploited ones float to the top across all customers at once.
Three ways to work together
- A recipe in your docs — a cron / deploy-hook snippet for your platform. No commercial ask.
- An app in your catalogue — a maintained one-click template (Forge, Ploi, RunCloud, GridPane, CloudPanel…).
- A resold security add-on — exploitation-ranked monitoring for your customers, co-branded today; white-label built with the first partner who commits.
The pilot
- 90 days, free, up to 200 sites, Team features on (fleet, SSO, seats, webhooks).
- A named contact, a written kickoff plan and a written readout of what it found, by email.
- Exit criteria agreed up front; you keep it only if it found something your current tooling ranked low.
What phpwarden does, in one paragraph
It scans the PHP engine (per branch and SAPI, because PHP backports fixes), Composer dependencies (with a reachability check), and WordPress core, plugins and themes — then ranks everything by what attackers are actually using: CISA KEV first, then EPSS, then CVSS. Of about 19,500 PHP vulnerabilities in its feed, 54 are known to be exploited (as of 14 November 2026); most scanners bury those under thousands of "criticals" nobody touches. The fleet dashboard puts every site you run on one screen, ranked the same way. It also checks each site from outside, scans your own code across the whole program, can block exploits of what each site runs inside PHP, and verifies WordPress files against the wordpress.org checksums. The data behind that →
Questions you'd reasonably ask
- Does my client data leave my servers?
- Only what you choose to send. The CLI runs offline; the dashboard receives scan results (package names, versions, findings) when you point it there — never source code or lockfiles themselves. Everything is in the privacy policy.
- Is this a WAF or malware scanner?
- No. It finds known-vulnerable components and ranks them by exploitation. Its shield, a PHP file loaded before your app, can block exploit attempts against the exploited vulnerabilities a site actually has, after a week of logging; it is not an edge WAF (no DDoS, bot or TLS handling) and not a malware scanner. For those we tell you which tools to use, and they run alongside phpwarden fine.
- What happens after six months?
- You decide. Stay on at founding pricing, drop to the free tier (your local scans keep working), or leave. The point of the program is to find out what this is worth to people like you, not to trap anyone.
- Who am I dealing with?
- One person, in the open. That's a feature for a program like this and a fair thing to weigh for a vendor relationship — ask whatever you need to.