Your data never leaves your servers.

fein reads your inbox, your calendar and your CRM to do its work, and that work runs inside your own environment. This page is the one to forward to the person who has to say yes: what fein touches, where it runs, and how you check every claim on it yourself.

Six guarantees, each one checkable.

None of these are policy promises. Each one is a property of how fein is built, and the code that makes it true is public.

  • Always self-hosted.

    fein runs in your environment, on infrastructure you control. It sends nothing to us.

  • Open source, end to end.

    Every line that touches your data is public, under Apache 2.0. Audit it before you run it.

  • One token, every surface.

    The dashboard, the API and the agent endpoint sit behind the same gate.

  • Private by person.

    Each person’s sensitive sources stay in their own layer inside the shared graph. fein enforces the scoping inside every query.

  • Every change is written down.

    Ingests, merges and review decisions are logged to an append-only audit trail, with the person or agent that made each one.

  • Nothing phones home.

    There is no telemetry, no analytics, and no control plane of ours for you to trust. Disconnect from the internet and fein carries on answering.

What fein reads, and where it stays.

fein connects to the systems your firm already runs: email, calendar, files, notes and CRM. It reads them with credentials you issue and can revoke, from inside your own environment. What it builds from them, the graph and its history, lands in your own database and stays there.

The deployment surface, in one paragraph.

  • Runs where you say. A machine you own, on-prem or in your own cloud account, deployed with Docker.
  • Credentials stay yours. Each source is connected with credentials your admin grants. Revoke one and that source goes dark to fein.
  • On managed setups, our engineer works inside your infrastructure with access you issue and can end at any time. Your data never reaches us either way.

Every fact keeps the sentence it came from.

One record per company. Dated, sourced, and never overwritten.

Halo Compute

company first seen 8 Nov 2024
  1. Opening a $30M Series A.

    We are opening a $30M Series A.

    Halo Compute, June update2 Jun 2026

    Raising a $4M seed.superseded 2 Jun 2026

    They are raising a $4M seed.

    Fwd: Halo Compute, seed deck8 Nov 2024

  2. Priya Nayar is VP Engineering. new record

    VP Engineering at Halo Compute.

    Priya Nayar, new position3 Jun 2025

  3. Two ex-Anthropic infra engineers.

    Both founders are ex-Anthropic infra.

    Coffee with Halo Compute21 Nov 2024

  4. Marcus Feld owns the conversation.

    Marcus Feld, Dev Raman, Halo Compute intro call.

    Halo Compute intro call14 Nov 2024

  5. Introduced by Dev Raman, co-investor.

    Marcus, worth twenty minutes.

    Fwd: Halo Compute, seed deck8 Nov 2024

Who should I bring into Halo Compute’s Series A?

Northwind Capital. They asked for more AI infrastructure exposure at the March review12 Mar 2026, and Halo Compute cleared the design partner objection in June2 Jun 2026. The warmest path in is Dev Raman, who forwarded the deck in 20248 Nov 2024.

Read from 4,180 records across your firm0.9s

What security reviews ask.

Does our data ever reach fein the company?

No. fein is deployed into your environment and runs there. There is no telemetry, no analytics and no control plane of ours. On a managed setup, the engineer works inside your infrastructure with credentials you issue and can revoke.

How do we verify any of this?

Read the code. Every line that touches your data is public on GitHub under Apache 2.0, and the binary you run is built from that source. A security review can audit the repository before anything is deployed.

How is access controlled inside the firm?

One token gates the dashboard, the API and the agent endpoint. Inside the graph, each person’s sensitive sources live in a private layer, and fein enforces that scoping inside every query, for humans and agents alike.

Is there an audit trail?

Yes. Every ingest, merge and review decision is written to an append-only audit trail with the person or agent that made it. Facts are never overwritten: a fact that stops being true is struck, dated and kept, so you can always see what the firm believed and when.

What happens to the data if we cancel or you disappear?

Nothing. The software is on your servers under a licence that cannot be revoked, and the graph is in your own database. There is no kill switch and nothing that expires. What stops with a cancelled contract is the upkeep, not the system.

Put this page in front of your security team.

Then put the repository in front of them too. If they have a question the code does not answer, we will get on a call with them.