#105Guide3 min

Add Hackaiz to a web agency’s services

Define an authorized security service, organize client work and deliver evidence without promising certification.

Hackaiz team · updated 21/11/2026

Illustration: an agency discusses several client projects.
Illustration: an agency discusses several client projects. Illustrative photo, not a screenshot.

01Sell a defined service, not a security promise

An agency can use Hackaiz to add a technical security review to an application delivery. Describe the service as a sequence: agree on the systems to examine, obtain authorization, run selected checks, explain findings and review corrective work. The deliverable is evidence about the chosen scope at a particular time, not a declaration that the entire application is safe. A review of a repository is not evidence that every deployed environment has been checked.

For example, your offer might cover the GitHub repository used to build a booking application and the client’s verified production domain. State separately whether a later verification after fixes is included in your own service agreement. This is an agency packaging decision, not a built-in partner entitlement. Do not promise discounts, commissions, leads or a Hackaiz certification: none is needed to describe this workflow.

02Organize client work on the eligible plan

Client spaces and white-label reporting are available only on Agency and Business plans. The Client spaces screen groups projects by customer, provides a monthly credit budget field and supports report branding. It is an organization tool in your account; do not present it as proof that the client has authorized testing or as an automatically provisioned client login.

Use a client name that your team can distinguish from similarly named projects. The agency name entered for reports concerns presentation, not the origin or certainty of the technical findings. All executed analysis and correction work uses credits. A plan does not start checks or activate monitoring by itself, and a client budget is not a quoted price per finding.

  1. 1Open Client spaces and fill in Client name and Your agency name (reports).
  2. 2Set Credits/month budget (empty = none) if you want a monthly budget for that space, then select Create space.
  3. 3Under Assign projects, choose the correct client space for each project; review Credits used this month when planning further work.

03Make authorization part of onboarding

Keep a written, signed client mandate for the exact systems, actions and dates covered by the engagement. Agency mandates contains a New record form for the client’s legal name, signatory, exact hosts, repositories, actions and validity period. File record submits a dossier for review; it is not instant permission to begin. Keep the signed original yourself rather than uploading it into that form.

A mandate never replaces technical ownership proof. Before any website or API analysis, verify the domain through the DNS TXT record _hackaiz, the HTTPS file /.well-known/hackaiz-verification.txt, or the project AI creating that file. Repository access requires the appropriate GitHub connection. For a third-party client host, the mandate must also be approved, current, unrevoked and cover the exact host and requested action.

04Deliver a readable report and a controlled next step

Use the customer severity groups Danger, To fix and To watch to explain what needs attention. Discuss the affected function and the evidence, not just a count of findings. For a booking service, explain whether a finding concerns another customer’s reservation or an exposed configuration value; label such examples as scenarios unless the report actually demonstrates them. Mention incomplete coverage explicitly.

Agree who reviews proposed fixes and who deploys. Where supported, Hackaiz prepares draft GitHub pull requests, which are proposed code changes for human review and approval; it never merges automatically. Your team still tests the application’s normal booking and cancellation paths. Offer monitoring only as an optional follow-up on connected systems, with the client’s authorization and credits for the work, not as an included promise of continuous protection.

Frequently asked questions

Was this article helpful?

Related articles