Secure SaaS & Full-Stack Product Engineering
Multi-tenant SaaS built on Next.js, TypeScript and Postgres with the parts that are painful to retrofit — tenant isolation, RBAC, audit trails and billing boundaries — designed in from the schema upward.
Verified Solvex Specialist
Verified by SolvexDirect specialist contact for Solvex engagements
What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.
Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.
What's covered
- Product architecture, data model and multi-tenancy strategy
- Next.js / React / TypeScript application engineering
- Postgres schema design with row-level security where it belongs
- Authentication, role-based access control and permission model
- Tenant isolation across storage, background jobs and object ownership
- Billing and subscription integration with entitlement enforcement
- Immutable audit logging for privileged and financial actions
- Observability, deployment pipeline and environment separation
What you receive
- Application source with architecture and data-model documentation
- Tenant isolation design and the tests that prove it holds
- RBAC matrix mapping roles to enforced server-side permissions
- Audit logging design covering privileged operations
- Deployment pipeline, environments and runbook
- Handover documentation and engineering walkthrough
Evidence and reporting
How the work is kept honest- Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
- A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
- Written scope firstAdvisory work runs to a written scope agreed before it starts, so what you receive is what was agreed.
Anyone holding a Solvex report can verify it publicly without seeing its contents.
Our boundaries
What this engagement does not do, stated before it starts.
- Regulatory certification (SOC 2, ISO 27001) is a separate governance engagement
- Ongoing feature development after handover is scoped separately
- Third-party processor behaviour remains the vendor's responsibility
- Content and business decisions inside the product remain yours
How this engagement runs
- 01
Intake
Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.
- 02
Scope and authorization
Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.
- 03
Investigation or build
Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.
- 04
Evidence
Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.
- 05
Delivery
A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.
- 06
Verification and retest
Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.
Questions we are asked
- Why does multi-tenancy need designing up front?
- Because tenant leakage is almost never a missing check in one endpoint — it is an ownership model that was never made explicit, so every new feature has to remember the rule. Deciding early where the boundary is enforced (schema, policy, or query layer) makes the rest of the product inherit it.
- Can you work on our existing codebase instead of starting fresh?
- Yes. We usually begin with a short architecture review so recommendations are grounded in what you actually have. Retrofitting isolation and audit into a live product is harder than building it in, but it is very often the right call commercially.
- Does this include a penetration test?
- Not by default, and we would rather it were independent. We build to a defensible standard and hand over the design; assurance carries more weight when the testers were not the builders.
Related services
Engineering
Secure API & Backend Engineering
Backend and API systems engineered around the authorisation model rather than around the endpoints — with schema validation, rate limiting, idempotent workflows and audit logging that make abuse expensive and incidents reconstructible.
Offensive / Testing
Web Application Penetration Testing
We attack your web application the way a skilled adversary would — safely, under a signed scope — and hand you a clear map of every exploitable weakness. You get proof, business impact and a fix-it plan, not a raw scanner dump.
Cloud / DevSecOps
Cloud Security Posture Management (CSPM)
Cloud environments drift into risk one change at a time. We assess and help you continuously manage your cloud security posture — catching misconfigurations, compliance gaps and risky changes before they become incidents.