Services

Five things people come to us for, in plain English, each with the starter engagement and the price behind it.

  • Penetration testing for startups in India

    A manual penetration test of your web app or API, sized for a startup: a fixed scope, a public price, evidence for every finding and a retest after the fix.

    Web app or API security check from ₹9,999

  • VAPT for SaaS and fintech products

    Vulnerability assessment and penetration testing for SaaS products and fintech systems, by hand, with the evidence an auditor or an enterprise customer asks for.

    Web app or API security check from ₹9,999

  • QA and release testing before you ship

    An exploratory and regression pass over your release candidate, on the paths that pay, with a defect list your developers can act on and a go or no-go note.

    Pre-launch release QA pass from ₹4,999

  • Load testing before the traffic arrives

    Load, stress and soak tests against a production-like environment: the breaking point, the bottleneck behind it, what to change first, and a re-run after the fix.

    Performance and load test from ₹6,999

  • DPDP Act and SOC 2 readiness

    A gap review against the Digital Personal Data Protection Act or the SOC 2 control set, with a prioritised fix list and the evidence an auditor will ask for.

    DPDP or SOC 2 readiness gap review from ₹7,999

How a development project runs

Scoped first, then built in two-week sprints, each ending with working software you have used. Every release goes through the testing track before it ships.

A development project. A first release is usually eight to sixteen weeks, and every release goes through the testing track before it ships.

  1. Discovery and scope

    One to two weeks

    We write down what the product does, who attacks it, what it must survive and what done looks like. You get a scope, an estimate and a threat model before any code.

  2. Design and build, in sprints

    Two-week sprints

    Working software every two weeks, with automated tests and a security review in each sprint. You see it, use it and redirect it as it grows.

  3. Test every release

    Inside each sprint

    Each release candidate goes through the testing track: load, penetration test, retest. Nothing ships with a known high or critical finding open.

  4. Launch and handover

    One week

    Production setup, runbooks, documentation and the final test report. The code and the infrastructure are yours. We can stay on by the sprint.

Send us a URL