> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Working with Coverbase

> Company profile and viability diligence, release cadence and roadmap transparency, early access to features in development, and how customers influence what Coverbase builds.

<div className="sr-only">For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.</div>

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](https://www.coverbase.com).

For the diligence file itself:

<CardGroup cols={2}>
  <Card title="Financial viability" icon="chart-line">
    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](mailto:security@coverbase.ai). We are asked this regularly by supervised institutions and do not treat it as an unusual request.
  </Card>

  <Card title="Reference customers" icon="users">
    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.
  </Card>

  <Card title="Security and compliance" icon="certificate" href="/security/compliance">
    SOC 2 Type II report, penetration-test attestation, completed CAIQ / SIG, subprocessor list, and BC/DR summary, all under NDA.
  </Card>

  <Card title="Commercial terms" icon="file-contract" href="/security/contract-terms">
    Notification, exit, renewal and notice, and the SLA exhibit.
  </Card>
</CardGroup>

<Tip>
  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.
</Tip>

## Release cadence and roadmap

<CardGroup cols={2}>
  <Card title="Public, dated changelog" icon="clock-rotate-left" href="/changelog">
    Every notable release is written up in the [changelog](/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.
  </Card>

  <Card title="Documentation ships with the release" icon="book">
    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.
  </Card>

  <Card title="Roadmap reviews with your account team" icon="map">
    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.
  </Card>

  <Card title="Early access" icon="flask">
    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.
  </Card>
</CardGroup>

## Influencing what gets built

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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Note>
  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.
</Note>

## Getting help day to day

| You need                                        | Go to                                                                       |
| ----------------------------------------------- | --------------------------------------------------------------------------- |
| Product help or an issue                        | [support@coverbase.ai](mailto:support@coverbase.ai), or your shared channel |
| Security reports, questionnaires, documentation | [security@coverbase.ai](mailto:security@coverbase.ai)                       |
| Platform status                                 | [status.coverbase.com](https://status.coverbase.com)                        |
| Commercial, roadmap, references                 | Your account team                                                           |
| The severity ladder and response clocks         | [Support, service levels and escalation](/security/support-and-slas)        |

## Related

<CardGroup cols={2}>
  <Card title="Support, service levels and escalation" icon="headset" href="/security/support-and-slas">
    What we commit to, and how escalation works.
  </Card>

  <Card title="Contract terms and exit" icon="file-contract" href="/security/contract-terms">
    Notification, data return, renewal and the diligence package.
  </Card>

  <Card title="Changelog" icon="clock-rotate-left" href="/changelog">
    What actually shipped, and when.
  </Card>

  <Card title="Trust and security overview" icon="shield-halved" href="/security/overview">
    The whole trust surface in one place.
  </Card>
</CardGroup>