Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
Some of what a buyer needs to know about Coverbase is not a feature. This page covers three of those: how you diligence us as a going concern, how you see where the product is going, and how you change it.

​
Due diligence on Coverbase as a company

Coverbase is a venture-backed company headquartered in the United States, building third-party risk and procurement software for regulated enterprises. Our customers include organizations in financial services, insurance, technology and healthcare, several of whom are named publicly on coverbase.com. For the diligence file itself:

Financial viability

Financial standing information, including funding position and, where your policy requires it, financial statements, is provided under NDA on request. Ask your account team, or security@coverbase.ai. We are asked this regularly by supervised institutions and do not treat it as an unusual request.

Reference customers

Reference calls with customers running comparable programs, including in regulated banking and financial services, are arranged on request. Ask for a reference matched to your regulator, your program size and your integration pattern rather than to a logo.

Security and compliance

SOC 2 Type II report, penetration-test attestation, completed CAIQ / SIG, subprocessor list, and BC/DR summary, all under NDA.

Commercial terms

Notification, exit, renewal and notice, and the SLA exhibit.
If Coverbase would become a critical third party for your program, ask us the same questions you would ask any critical vendor: financial standing, key-person dependency, business continuity, exit path, and escrow if your policy requires it. We would rather answer them during the evaluation than during your first examination.

​
Release cadence and roadmap

Public, dated changelog

Every notable release is written up in the changelog, dated, with what changed and links to the documentation for it. It is public, so you can see the delivery cadence for yourself before you sign rather than taking a slide’s word for it.

Documentation ships with the release

Feature documentation is updated in the same release, not months later. The changelog entry links to it. This page and the guides beside it are the current state of the product.

Roadmap reviews with your account team

Your account team walks the forward roadmap with you on a recurring cadence, under NDA, and will tell you where a capability you need actually sits rather than answering “on the roadmap” to everything.

Early access

Capabilities in rollout are released behind per-organization feature flags. Customers who want a capability early can be switched on ahead of general availability, and beta features are labeled as such in this documentation so you always know what you are looking at.

​
Influencing what gets built

Coverbase is small enough that the people who build the product are reachable, and deliberately runs that way.
1

Raise it with your account team

Every customer has a named account contact who routes product requests directly to the team that owns the area. Enterprise customers have a shared channel with Coverbase staff, so a request does not have to wait for a scheduled call.
2

Bring the problem, not just the feature

The requests that move fastest arrive as a described workflow, an examiner expectation, or a report your program has to produce. A request framed that way tells us what to build; a feature name usually does not.
3

Partner on it while it is being built

Where a capability matters enough to your program, we will build it with you: scoped together, released to your organization behind a flag first, and iterated against your real data before general availability. Ask your account team to set that up explicitly if it is what you need.
4

Hold us to the date

A committed date belongs in writing with your account team. Ask for it, and ask what happens if it slips.
If formal design-partner status, a named product contact, or roadmap-influence commitments matter to your evaluation, say so during the evaluation rather than after. These are arrangements we make, and they are far easier to agree while the commercial conversation is open.

​
Getting help day to day

Support, service levels and escalation

What we commit to, and how escalation works.

Contract terms and exit

Notification, data return, renewal and the diligence package.

Changelog

What actually shipped, and when.

Trust and security overview

The whole trust surface in one place.