01 / UNDERSTAND
Start with the evidence.
Review focused checks on your repository. See the affected file, the supporting evidence, and why each finding needs attention.
Fenrix / In development
Move forward.
Know where you stand.
A clear path from security findings to tested changes.
Understand the issue. Review the fix. See the evidence.
Built for teams who want to understand what they ship.
Tenant Notes
Clarity at every step.
FindingReview customer data isolation
ProposalAn ownership policy, ready for review
EvidenceBefore-and-after database checks
- 01 InspectTrace findings to source.
- 02 ReviewUnderstand the proposed change.
- 03 VerifyTest the supported behavior.
A more considered workflow
Less ambiguity.
More informed decisions.
02 / REVIEW
Keep control of the change.
Inspect a proposed database policy before testing it. Changes stay proposals for your review; the preview does not deploy them.
03 / VERIFY
Look at both sides of access.
For supported database models, test that private records stay private and that permitted operations still work.
Inside the development preview
Focused by design.
Explicit about scope.
Fenrix v0.5 is a local product preview. These are its current capabilities, not a promise of complete application coverage.
- Eight focused static checks
- Review signals covering selected access-control, credential, web-security, and supply-chain patterns.
- Supported PostgreSQL verification
- Test a declared single-table ownership model with two synthetic users in an isolated local database.
- A record you can revisit
- Compare assessments and export findings and saved verification evidence as PDF or JSON.
- Clear limits on every result
- Static findings need contextual review. Database checks do not certify the security of a deployed application.
Before you get started
A few useful answers.
Can I use Fenrix online today?
The hosted application is not publicly available yet. The current version runs locally. Email us to discuss your use case and availability of early access.
Does Fenrix automatically change my code?
No. The current preview presents proposed changes for review. Supported database tests use a temporary environment and synthetic data; they do not alter your production database.
What does a passing verification mean?
It means the defined database assertions passed for the supplied supported schema and candidate policy. It does not establish that an entire application is secure or compliant.
What should I include in an early-access request?
A short description of your project, its technology stack, and the security workflow you want to improve. Please do not send source archives, passwords, API keys, or customer data.
Help shape what comes next
Let’s talk about
what you’re building.
Tell us about your project and what you need from an application assurance tool.
Email about early access
khushanivivaan@gmail.com
Opens your email app. No account is created and no mailing-list signup is submitted on this website. Privacy information