-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
b742299
commit a87392b
Showing
1 changed file
with
15 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,17 @@ | ||
# ApiGov | ||
API data governance tool that captures client API calls, visualize and monitor data flows | ||
API data governance tool that captures client API calls, visualize and monitor data flows. | ||
|
||
Refer to our [Architecture doc](./doc/architecture.md) for more details. | ||
|
||
# Why is this tool useful? | ||
|
||
|
||
# Why do we create this tool? | ||
In the past couple of years, we saw increasing usage of 3rd party APIs. Also, more and more data are shared via APIs. | ||
|
||
In my previous job doing cyber security risk consulting, I saw companies lacking visibility around data shared via APIs. With GDPR and CCPA, it is becoming mandate for companies to have data governance around their APIs. | ||
|
||
My co-founder has extensive experience is DevOps and software development. He wanted to have a tool for client API monitoring, beyond exgress logging. He was constantly fighting with client API outages and could not optimize the API usage based on needs. | ||
|
||
We are both excited to build a tool that can log API calls, visualize API data flows, send alerts for outages and suspicious data flows. | ||
|