1. Empty inside.
Even through an open door, anyone who shouldn't be there reads nothing. The room answers, and the room is empty.
Independent security for software teams
Access is not reach.
For the intruder, every door opens onto an empty room. For you, it's quiet. NIGHTMARE.sh builds and tests your SaaS so that access is not reach, and shows you where it still is.
6 questions. We never ask for an IP, a host, a token or a key.
Scroll to follow the crossing

Forged under real fire
NIGHTMARE.sh began as the defense of a SaaS in production. It took an automated attack against its public entrances. The same kind of entrance almost every modern product has: an API, a login, a form.
The attacker got in. That part was never in doubt, because those doors are public by design.
What mattered was what the doors opened onto. The answers came back "OK", and they came back empty. We saw no sign that any protected data was read. The structure held.
We also have to tell you the other half. Our emergency response was improvised, and it cost us availability. Our own containment took part of our own service down for a while. The attack did not do that. Our panic did.
We took two lessons from the same night.
One: build so that getting in leads nowhere. Two: never improvise the response. Rehearse it, before the bad night.
No names, no dates, no numbers on this page. This is what happened, in the shape we are willing to tell it.
Read the doctrine ↓The method

Most security is a wall: one line, one bet that nothing gets past it. But much of what you run is open on purpose. A public key in the front end. An API that generates itself. A login by link. When something walks through, you are blind, and you improvise.
The NIGHTMARE.sh Doctrine starts from the other end. Assume the entrance will be easy. Design what comes after.
Access is not reach.
Even through an open door, anyone who shouldn't be there reads nothing. The room answers, and the room is empty.
The deeper someone goes, the more you know about them. Each step inward leaves a trace you can read.
Every route can be shut, and the response is rehearsed in advance. It is never invented during the incident.
The Doctrine is a way of building and responding. It is not a product you install, and it does not promise that nothing will ever happen. It promises that we know what we are doing when it does.
Find out where your system stands → Start the diagnostic6 fronts
Everything we do answers a question you already have. Here are the 6.

Who can read what, and how would we know if they shouldn't?
What can an outsider reach right now?
If one machine falls, what else falls with it?
Where can our own code be turned against us?
Would we notice? And would the right person hear it?
Who acts when an incident starts?
Weak at one front, and the others carry the load. Solid at all 6, and an intruder has nowhere to stand.
Answer the 6 → Start the diagnosticDiagnostic
We never ask for an IP address, a hostname, a token, a password or a key. Answer from what you know. If you don't know, say so: that is an answer too.
For each question, choose Yes, Partly, No or I don't know.
Plans
You do it. You do it with us. We do it for you. Choose how far you want us to go.
You do it.
Developers and technical founders building a SaaS, alone or in a small team, who want to know in an afternoon whether there's an obvious hole.
3 skills that run with your AI coding agent on your own project: pentest, hardening and incident response. Each finding comes with the evidence, the risk, a fix and a retest. Updates when the skills change.
Name, email and WhatsApp. A project that is yours to test.
Fill the form and download right away.
US$ 0. 3 fields instead of money.
Takes about two minutes.
Your system, your terms. We never see your project.
You do it with us.
CTOs and tech leads of SaaS companies already billing customers, with a team to fix things but no security specialist, and often a date: a big customer's questionnaire, an investor, a launch.
Written scope and a delivery date, before you pay. A scan across the 6 fronts. A report that says what to fix first, and why. Guidance while your team fixes. One retest of the findings you fixed.
Written authorization. A test environment you control. Test accounts you create and revoke. One contact on your team. Optional: read access to the code.
You request, we agree scope, you get the delivery date in writing, then you pay.
US$ 10,000, one time.
One retest included. Delivery date in writing before you pay.
We work in a test environment. We never ask for production access, passwords, keys or server addresses.
We do it for you.
Founders and CEOs of SaaS companies where an hour of downtime or a leak costs more than they want to find out, and nobody is in charge of security.
The Doctrine applied to your system and kept up as it changes. A written, rehearsed incident response. Response terms in your contract: channel, hours covered, time to first action. The right to display Protected by NIGHTMARE.sh.
An application and a conversation. Time to map the system, write the runbook and rehearse it with us.
You apply. We talk. If we fit, we deploy and rehearse. Coverage starts after the rehearsal.
US$ 80,000 / month (about US$ 1M a year). The monthly fee starts when coverage starts.
By application · Coverage starts after onboarding
We accept a limited number of Protection clients, and we cover only what we have rehearsed.
Not sure which? Take the diagnostic. It recommends one plan, and shows you the rule it used.
Because 3 fields is the price, and we would rather say so. In return you get the whole kit and a notice when it's updated. You see what's inside before you fill anything in.
Two reasons. We message you when the skills change (a new probe, a correction). And one person from NIGHTMARE.sh will message you once, to ask how it went. That's all. Reply "stop" and it stops.
No. We don't sell or share your data. You can leave in one step and ask us to delete it. Our privacy policy is next to the button, not buried in the footer.
The skills require an authorized environment, low request rates and stopping at the first sign of harm. Those rules are on the page before the form.
A checklist is a list. These skills follow the sequence of a real attack and hand you evidence, a fix and a retest for each finding. The page shows an example, marked as fictional.
This is the door in. You get a real tool. We get to talk to people who ran it. When your list of findings outgrows your team's capacity to order it, there's the Assessment.
It was built for SaaS products with a database behind an API, an edge or proxy, a server and containers. It does not cover every stack. The install section lists the tools we have actually tested.
You're not buying a PDF. You're buying the order (what to fix first), the reason, the guidance while your team fixes, and a retest that confirms the fix worked.
A scanner lists. It doesn't know what an attacker would do first in your project, it doesn't sit with your team, and it doesn't confirm the fix.
No. We work in a test environment that you control, with test accounts you create and revoke, under written authorization. Production only if you ask and it's written into the scope. We never ask for passwords, keys or server addresses through this site, by email or in chat.
You get the delivery date in writing, before you pay. If we can't meet the date you need, we'll tell you before you pay.
One retest of the findings you fixed is included. You get a record of what we verified as fixed. New findings from the retest go in the record. They don't open another included round.
That's why the report is ordered: item one matters most. If there's truly no time and no people, that's a sign of 24/7 Protection.
We don't list clients and we don't display badges we haven't earned. What we offer instead is the origin, the method, and the free skills, which you can judge before paying us anything.
Then the report says what is solid, and why. That is also what you show a big customer or an investor. We won't promise a number of findings.
It is. It's for companies where an hour of downtime or a leak costs more than the year. If that isn't you, the Assessment is the right plan, and we'll say so. The monthly fee starts when coverage starts.
Because we accept a limited number of clients and cover only what we've rehearsed on your system. Anyone who sells this in one click hasn't rehearsed anything.
Because improvised response is expensive, and we know that from our own history. First we map your system, apply the Doctrine and write the runbook with you. Then we rehearse it. Then we cover.
Channel, hours covered and time to first action are written into your contract before coverage starts. We don't put on this page a number that isn't in your contract.
Minimum term and notice period are written and shown to you before you sign. No hidden renewal, no surprise penalty. If you leave, you keep everything we built for you: the runbook, the configuration and the documentation. The badge leaves with the protection.
Tools block patterns. They don't respond to incidents. Someone has to decide what to close without taking the service down, and that someone needs a runbook they've rehearsed.
That happened to us, once, in our own origin story. It's the reason nothing is covered before it is rehearsed.
A small, independent firm that takes few clients on purpose. We don't publish a team size, and we won't use words for staff we can't show.
Interested in NIGHTMARE.sh? Leave a way for us to reach you.
6 questions. A plain answer. No IP, no host, no token, no key.
Start the diagnostic