llms.txt
Compare with other sites' llms.txt files →# Railo
> Railo fixes security findings as reviewed pull requests in the customer's own GitHub repository, and records the evidence: what was found, what changed, how each fix was checked, who reviewed it and when it merged. Teams send findings from a pentest report, a code scanner (Snyk, Semgrep, CodeQL, GitHub code scanning) or a customer's security questionnaire. Railo also publishes a free GitHub Action that suggests rule-based fixes on new pull requests.
Railo's founders are Zarif Latif (Founder & CEO) and Kazi Tasfin Mahmud (Co-founder & COO). Railo is headquartered in Dhaka. Contact: zarif.latif@railo.dev.
## What Railo sells
- **Fix Sprint:** USD 1,500 fixed price for one repository and up to 25 findings; larger reports are quoted before work starts. A Dependency Sprint is the same sprint applied to a Dependabot, Snyk or npm audit backlog, delivered with CI green. Pull requests within 5 business days and an evidence pack after that. Railo signs the customer's NDA before receiving access, opens pull requests and never pushes to the customer's branches, and works in a private clone that is deleted when the sprint ends.
- **Pentest close-out:** USD 4,000 to 6,000 per pentest report, quoted after Railo reads the report. Every code-level finding in the report, across up to 25 repositories, closed inside the retest window, with the evidence pack keyed to the report's own finding IDs.
- **Fix Desk:** from USD 1,500 a month, month to month. New findings fixed every month, with a monthly evidence report.
- **Retest promise:** if the tester's retest still finds an in-scope finding Railo marked fixed, Railo fixes it again at no charge, until the retest passes it or Railo explains why a code change would be wrong. Railo does not promise what a retest will find elsewhere.
- **Not included:** infrastructure and cloud settings, architecture changes, decisions about who may see what, findings outside the agreed list, testing of any kind, merging on the customer's behalf, and any promise that the whole application is secure.
- **Free GitHub Action:** runs on the customer's own GitHub Actions runner, scans the files changed in a pull request, and suggests fixes on the changed lines as GitHub suggested changes. Source code is not sent to Railo.
- **Fix Gate (free, beta):** a GitHub Action that verifies any security-fix pull request, whoever wrote it, on five checks: the targeted finding is gone, nothing new appeared in the changed lines, the changed files still parse, the tests did not newly fail, and the validator the fix adds holds against a fixed list of known bypass payloads for its weakness class (that one function runs in a restricted subprocess on the repository's runner, on pull_request events only). Each check is pass, fail, nothing to check or not run; not run is never reported as a pass. Rule-based, runs on the repository's own runner.
## How fixes are made
- Fixes the engine knows are written by deterministic rules, not by a language model. Railo's engine fixes common issues in Python, JavaScript and TypeScript, Java, Go and PHP; Ruby and C# are fixed by hand.
- Every fix, whoever wrote it, is rescanned: the finding must be gone and nothing new may appear. The customer's CI runs on every fix pull request, and the customer's team reviews and merges.
- A finding that cannot be fixed safely is returned with an explanation and a recommended change, and is listed as still open in the evidence pack.
## Who it is for
- Software teams that must close findings before a pentest retest, an audit window (for example SOC 2 or ISO 27001) or a customer's security review.
- Pentest firms and security consultants who refer clients whose findings need fixing (20% referral fee on the client's first engagement).
## What Railo is not
- Not a penetration test and not an auditor. The evidence pack is a record of each finding, its fix and how it was checked; it is not a compliance certificate, and the customer's auditor decides what it counts towards.
## Published results
- [We read all 162 automatic fixes. 95 were wrong.](https://www.railo.dev/research/autofix-11-repositories) (first published on [dev.to](https://dev.to/zarif_latif_114a9ed729d58/how-we-tested-railo-on-11-public-repositories-34i2), 16 October 2026): 923 findings across 11 public repositories; 162 automatic fixes proposed and read; 95 should not have been proposed, mostly edits to vendored libraries, test data and seed data; 67 kept; none broke a file's syntax. The engine was changed as a result.
- [A pentest report is the start of the work](https://dev.to/zarif_latif_114a9ed729d58/a-pentest-report-is-the-start-of-the-work-here-is-what-the-end-should-look-like-4hag): what the end of remediation should look like.
## Guides
- [Pentest findings, fixed before your retest](https://www.railo.dev/pentest-remediation): who fixes pentest findings, published retest windows (Triaxiom, HackerOne, Cobalt), what a fixed finding comes back with
- [Overdue vulnerabilities in Drata or Vanta](https://www.railo.dev/guides/drata-vanta-vulnerability-sla): default deadlines, the tests that fail, and the options
- [Vulnerability remediation evidence for SOC 2](https://www.railo.dev/guides/soc-2-vulnerability-remediation-evidence): what CC7.1 and CC8.1 say and the records teams usually keep
## Pages
- [Home](https://www.railo.dev/): the Fix Sprint, how it works, pricing and questions
- [Sample evidence pack](https://www.railo.dev/sample-evidence): a real evidence pack from a rehearsal sprint on OWASP NodeGoat, with a CSV download
- [Audit evidence](https://www.railo.dev/compliance): what Railo records for every fix
- [Partners](https://www.railo.dev/partners): for pentest firms and security consultants, by referral or under the firm's own name
- [Security and data handling](https://www.railo.dev/security): what Railo touches and what it never does with your code
- [Free GitHub Action](https://www.railo.dev/action) and [setup guide](https://www.railo.dev/docs/github)
- [Fix Gate](https://www.railo.dev/fix-gate): the free check for security-fix pull requests, with the workflow file and the inputs
- [Configuration](https://www.railo.dev/docs/configuration)
- [Support](https://www.railo.dev/support)
## Optional
- [Railo GitHub Action repository](https://github.com/IWEBai/railo-action)
- [Fix Gate Action repository](https://github.com/IWEBai/fix-gate-action)
- [Fix Gate on GitHub Marketplace](https://github.com/marketplace/actions/fix-gate)
- [Privacy Policy](https://www.railo.dev/privacy) and [Terms of Service](https://www.railo.dev/terms)