Knoxy
Security & data

Your data never becomes our data

How Knoxy is built to keep your code and your customers' data under your control, in India.

Where Knoxy runs

  • Knoxy is installed in your own AWS account, in the Mumbai region (ap-south-1).
  • The app has no public address. People reach it only from your office network, through an encrypted tunnel.
  • Outbound traffic is limited to an allow-list (your Git host and AWS services). Everything else is blocked and logged.

What we (Hubknox) can see

  • Your code, prompts, answers and customer data stay in your account.
  • Our control plane receives only licence, version, health and usage counts, over an outbound connection that Knoxy opens.
  • We have no standing access into your account.

How every AI request is guarded

  • Secrets (API keys, tokens, passwords, private keys) and personal data (Aadhaar, PAN, phone, email, bank details and more, including Indian-script digits) are masked before any model sees them.
  • A separate safety model checks each request for prompt injection and harmful content, in English and Indian languages. If it cannot decide, the request is blocked.
  • Only models that process data in India are allowed. Routes that can leave India are refused when Knoxy starts.
  • Answers are scanned on the way back, and spend is limited per person, team and customer.

AI models

  • Models are called through Amazon Bedrock in your own AWS account, over a private network connection.
  • AWS does not use Bedrock prompts or answers to train models, and Knoxy keeps Bedrock's prompt logging switched off.
  • Knoxy can switch between model vendors without changing your setup, so one vendor's outage does not stop your teams.

Evidence and audit

  • Every AI request is recorded with who, what task, which model, what was masked, cost and outcome. Never the prompt or the answer.
  • In production, records are kept in write-once storage that no one, including administrators, can edit or delete during the retention period.
  • Account activity, configuration changes and security findings are monitored continuously, with alerts for anything risky.

Access

  • Sign-in through your own identity provider (for example Microsoft Entra ID, Okta or Google Workspace). Knoxy never stores passwords.
  • Roles come from your directory groups: developer, lead, release manager, admin, auditor.
  • Changes need maker-checker approval: authors cannot approve or release their own work.
Knoxy is in early access. Security questionnaires, architecture details and our responsible-disclosure contact are available on request: admin@hubknox.ai. Request a demo to see it on your own code.