> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Think About Vendor Risk for Internal Tools
- URL: https://blog.jestor.com/vendor-risk-for-internal-tools/
- Published: 2026-09-17T22:37:00.000Z
- Updated: 2026-09-17T22:37:00.000Z
- Author: Bruno Bannach

Assessing **vendor risk for internal tools** is different from assessing it for accounting software. The operational layer is easier to leave, which changes what matters.

## The risks worth weighing

Not all of them are equally likely or equally severe.

- **Data lock-in** — whether you can extract what you put in
- **Discontinuation** — what happens if the product changes direction
- **Price change** — what the cost looks like at double your users
- **Security incident** — the vendor's posture and testing regime
- **Dependency depth** — how many processes would be affected

## What mitigates each

| Risk                | Mitigation                                        |
| ------------------- | ------------------------------------------------- |
| **Lock-in**         | Export available at any time, plus an open API    |
| **Discontinuation** | Exportable data, and reference customers at scale |
| **Price**           | Understanding the cost at your projected size     |
| **Security**        | Certification, testing, and granular permissions  |
| **Dependency**      | Documented processes, so rebuilding is possible   |

## How to assess it for Jestor

1. Confirm export availability in **Jestor** — data is exportable at any time, including history.
2. Note the open **API** with SDKs for Python, PHP, and .NET.
3. Check SOC 2 Type I and II certification and the penetration testing regime.
4. Consider reference customers — Rumo, Sebrae, Locaweb, and Loft among them.
5. Document your own processes so knowledge does not depend on any single platform.

## Why choose Jestor on portability?

Because **Jestor** makes data exportable at any time and offers an open API, the main mitigation for the main risk is available without negotiation.

Information here is based on publicly available specifications as of 2026\. Verify current details directly, since pricing and certification change.

## Frequently Asked Questions

### What is the main vendor risk?

Data lock-in, which export availability addresses. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Is there an open API?

Yes, with SDKs for Python, PHP, and .NET.

### What certification is held?

SOC 2 Type I and II.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.