Private by design

One workspace for each company, hosted where your data must stay, with a named person approving every consequential action. Here is how it is protected, what you can ask for, and what we don't do yet.

Your systems

EmailZohoGoogle DriveTallyFile server
Access you grant

Your private workspace

Your brand
Named accounts
Your documents
Approvals
Audit trail

Isolated · backed up daily, encrypted

Model you choose
ClaudeOpenAIGemini
Named approver
Approvedthen it goes out

Other companies

Workspace B
Workspace C

Separate, never pooled

private workspace per company
0
private workspace per company
actions sent without a named approver
0
actions sent without a named approver
deployment options
0
deployment options

Hosted where your data must stay

Start managed and isolated, or have the workspace deployed inside your own cloud or your own data centre. The workspace, the approvals and the audit trail are the same in each.

  1. 01
    Available

    Managed by Inference

    An isolated workspace we host, run and maintain for your company alone. The fastest way to a first workflow in production.

    Runs in
    Infrastructure we operate
    Operated by
    Our team
    Isolation
    Own workspace and storage
  2. 02
    On request

    In your cloud

    Deployed inside your own AWS, Azure or GCP account, under your policies and network rules. Scoped per project.

    Runs in
    Your cloud account
    Operated by
    Our team, on access you grant
    Isolation
    Your account boundary
  3. 03
    On request

    On-premise

    Installed on your servers, inside your network, for teams whose documents cannot leave the building. Scoped per project.

    Runs in
    Your data centre
    Operated by
    Agreed with your IT team
    Isolation
    Your network perimeter

Data residency, on request

If your policy or regulator requires a specific hosting region, including India, tell us at the start. We will confirm in writing where the workspace, its storage and its backups run, and which model provider region your work is sent to.

On request

Every account has a name on it

Everyone signs in as themselves. There are no shared team passwords, and passwords are stored hashed, never in plain text.

Members and roles

Example

  • Head of CommercialApprover
  • Tender EngineerPreparer
  • Quality ManagerApprover
  • Plant AccountsViewer
  • Inference supportOperator

Our support staff appear as named operators. They maintain the workspace and never approve on your behalf.

Who prepared it, who approved it, what was sent

Quotations, bids, filings and customer messages wait for a named person before they leave. The record keeps all three answers together, with the time and the source documents, so an auditor or your own board can follow any decision back.

  • Approval gates are set per workflow, by your team
  • Chat cannot grant itself more authority
  • We never submit on a portal such as GeM for you

Audit trail · Tender 2025/114

Example

  1. 09:12

    Workspace read tender NIT and 2 corrigenda

    NIT.pdf · 184 pages

    Prepared
  2. 09:40

    Tender Engineer prepared compliance matrix, 3 deviations

    Section 6, clauses 6.2 to 6.14

    Prepared
  3. 10:05

    Workspace held for approval by Head of Commercial

    Held
  4. 11:20

    Head of Commercial approved offer and deviation list

    Approved
  5. 11:24

    Tender Engineer sent techno-commercial offer to buyer

    Offer v3.pdf · approved copy

    Sent

Prepared by

Tender Engineer

Approved by

Head of Commercial

Sent

Offer v3.pdf

Your data, under your control

01

Your documents stay in your workspace

Tenders, contracts, drawings and correspondence live in your company's own workspace and storage. They are never pooled with another company's or used to serve anyone else.

02

Integrations use only the access you grant

Email, Zoho, Google Drive, Tally and file servers connect with the scope you choose. Any of them can be disconnected, and the workspace stops reading from it.

03

The model provider is your choice

The workspace is model-agnostic. Your policy decides whether work goes to Claude, OpenAI or Gemini, and it goes only to the provider you pick.

04

Answers point to their source

Every draft shows the document, page or clause it came from, so a reviewer checks evidence rather than trusting a summary.

Kept, restorable and yours to take

Mission-critical work cannot depend on one vendor staying convenient. These are written into how we run every workspace.

  1. Daily

    Encrypted backups

    Your workspace is backed up every day and the backups are encrypted.

  2. Tested

    Restores we actually practise

    We restore from backups on purpose, because a backup nobody has restored is only a hope.

  3. Exit

    A way out, written down

    An agreed exit path for your data, in formats you can use. You are not held in place by how it is stored.

  4. Yours

    The right to keep running your version

    You keep the right to go on running the version installed for you. The monthly service covers fixes, security and upkeep on top of that.

Evidence for the audits you answer to

Compliance belongs to your company. The workspace is built to support it, with records and audit trails your security, compliance and IT teams can hand to an auditor or a regulator.

  • ISO 27001Information security

    Access records, role assignments, change history and backup evidence you can place in your ISMS and show an auditor.

  • DPDP Act 2023Personal data

    A clear record of where documents sit, who accessed them and when, plus a documented export and exit path.

  • CERT-In DirectionsIncidents and logs

    Timestamped activity records that support your incident reporting and log requests.

  • RBI, SEBI, IRDAIOutsourcing and cyber

    Deployment choice, a written exit plan and straight answers for your outsourcing due diligence and right-to-audit questions.

What we don't hold or do yet

We would rather you hear these from us than find them in a review. If one of them matters for your company, tell us early.

  • Not held

    Security certifications

    We do not hold SOC 2 or ISO 27001 and will not suggest otherwise. The workspace supports your compliance work; it does not certify it.

  • Not built yet

    Single sign-on

    Signing in through Microsoft, Google Workspace or another identity provider is not built. Today everyone signs in with a named account.

  • Not built yet

    Multi-factor sign-in

    A second factor at sign-in is not built. Today accounts rely on a password and server-side sessions that expire.

Send us your security questions

Questionnaires, vendor assessments, outsourcing due diligence. We answer in writing, including the gaps, and the person who answers is the person who builds your workspace.