Private by design

One workspace for each company, hosted where you choose, with a person approving before anything important goes out. Here is how it is protected, and what we don't do yet.

Where it runs

The workspace, the approvals and the audit trail are the same in each.

Managed by General Inference (available now)

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

In your cloud (on request)

Deployed inside your own AWS, Azure or GCP account, under your policies and network rules. Our team runs it on the access you grant. Scoped per project.

On-premise (on request)

Installed on your servers, inside your network, for teams whose documents cannot leave the building. Run as agreed with your IT team. Scoped per project.

Need a specific hosting region, including India? Tell us at the start. We confirm in writing where the workspace, its storage and its backups run, and which model provider region your work goes to.

Who can get in

Named accounts, no shared logins

Everyone signs in as themselves. Passwords are stored hashed, never in plain text.

Roles decide who sees and approves what

People see the workspaces, files and actions their role allows. Preparing a draft and approving it are separate permissions.

Sessions expire

Sessions are held on the server and expire, so nobody stays signed in forever and access can be ended from one place.

Our support staff are named too

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

Approvals and the audit trail

Quotations, bids, filings and customer messages wait for a person to approve them before they leave.

The record keeps who prepared it, who approved it and what was sent, with the time and the source documents, so an auditor or your board can follow any decision back.

  • Your team sets the approval steps for each workflow.
  • Chat cannot give itself more authority.
  • We never submit on a tender portal for you.

Your data

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.

Integrations use only the access you grant

Email, Zoho, Google Drive, Tally and file servers connect with the scope you choose. Disconnect any of them and the workspace stops reading from it.

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.

Model choice

The workspace works with Claude, OpenAI or Gemini. Your policy decides which, and your work goes only to the provider you pick.

Backups and a way out

Daily encrypted backups

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

Restores we practise

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

A written exit path

An agreed way out for your data, in formats you can use.

Keep running your version

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

Evidence for your audits

Compliance belongs to your company. The workspace is built to support it with records your teams can hand to an auditor or regulator.

ISO 27001

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

DPDP Act 2023

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

CERT-In Directions

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

RBI, SEBI, IRDAI

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

What we don't hold or do yet

Security certifications: not held

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

Single sign-on: not built yet

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

Multi-factor sign-in: not built yet

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.

Email us