FEDERAL INDEXSecurity
Written to be forwarded. If you are reviewing Federal Index on behalf of someone else, this page is meant to answer your questions without a call — including the ones where the answer is no.
Start here, because most vendors bury it
Federal Index is a new company. We would rather you learn the following from us now than from a questionnaire in six weeks.
- No SOC 2 report. Not Type I, not Type II. We have not begun an audit.
- No ISO 27001 certification.
- No third-party penetration test has been performed against the platform.
- No SSO, SAML or SCIM today. Access is email and password with role separation.
- No customer references. We have not yet sold to anyone, so there is nobody for you to call. Anyone claiming otherwise is not us.
If your procurement process requires a SOC 2 report, we will not pass it today, and we would rather say so before you spend a cycle on us.
Isolation is enforced by the database, not by our application code
This is the part most vendors do not describe, and it is the part that matters. Tenant separation in Federal Index is a Row-Level Security policy inside PostgreSQL. Every tenant-scoped table carries a policy that filters rows by organisation before any query returns. A bug in our application layer cannot leak another customer's data past it, because the application layer is not what is enforcing the rule.
- Enforced at the strongest available layer. Policies live with the data, not in a middleware check that a future code path could forget to call.
- Role separation inside a customer. Employees see the dashboards their role requires. A seat is scoped, not just authenticated.
- Append-only audit surfaces. Ingest and publication records reject updates and deletes at the database level, so the trail cannot be quietly rewritten.
- Nothing tenant-scoped is public. The one public storage bucket holds rendered marketing images and nothing else.
And the honest history: row-level security was not enabled when the schema was first
applied to the live project — it was applied with the option that skips it. A platform
linter flagged it, and migration 0016 exists specifically to enable and enforce
it across every table in the public schema. We are telling you this because a security page
that reads as though nothing ever went wrong is not a security page.
Correctness is a security property here
For a regulatory-intelligence product, a wrong answer delivered confidently is a worse outcome than downtime. The control for that is deterministic and sits in front of anything a customer sees: every claim must resolve to a document in the corpus and a citation string within it. Work that cannot be traced to a primary source is blocked rather than published — it is not a scoring threshold or a confidence percentage, it is a hard gate that fails closed. Structural changes to the system require a human to approve them.
Subprocessors
These third parties process data on our behalf. The same list, with the purpose of each, appears in our Privacy Policy, which is the binding version.
Supabase
Application database and authentication. Hosts customer records under the policies described above.
Railway
Runs the API and the ingestion scheduler.
Vercel
Serves this website. No customer data.
Anthropic
Language models used for interpretation and routing.
Stripe
Payments. We do not store card numbers.
Resend
Transactional email — briefs, alerts and account mail.
Reporting something
If you believe you have found a vulnerability, write to hello@federalindex.us with enough detail to reproduce it. We do not currently run a paid bounty programme and will not pretend otherwise. We will acknowledge you, and we will tell you when it is fixed.
Federal Index is an independent, privately operated service. It is not a government agency and is not affiliated with or endorsed by any of the government publishers it reads.