-
Notifications
You must be signed in to change notification settings - Fork 3
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
Showing
1 changed file
with
7 additions
and
19 deletions.
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,25 +1,13 @@ | ||
<div align="center" alt="Warrant"> | ||
<a href="https://warrant.dev/?utm_source=awesome-authz" target="_blank"> | ||
<img src="https://warrant.dev/images/logo-primary-wide.png" width="300"> | ||
</a> | ||
</br> | ||
</br> | ||
</div> | ||
# Edge Agent | ||
|
||
# Warrant Edge Agent | ||
## What is the Edge Agent? | ||
|
||
## What is the Warrant Edge Agent? | ||
The Edge Agent is a lightweight service that can process access check requests. It can be deployed in any cloud environment to minimize the latency of access check requests from services using WorkOS FGA to enforce authorization. The Edge Agent serves access check requests from a local cache and keeps caches up-to-date from the cloud service. | ||
|
||
The Warrant Edge Agent is a lightweight service that can process Warrant access check requests. It can be deployed in any cloud environment to minimize the latency of access check requests from services using Warrant to enforce authorization. The Edge Agent serves access check requests from a local cache and connects to `stream.warrant.dev` to receive updates as access rules are modified in order to keep it's cache up-to-date. | ||
## Should I use the Edge Agent? | ||
|
||
## Should I use the Warrant Edge Agent? | ||
Teams with strict latency and reliability requirements can deploy the Edge Agent in their own infrastructure for improved latency and availability. | ||
|
||
Teams with strict latency and reliability requirements can deploy the Warrant Edge Agent in their own infrastructure for improved latency and availability. | ||
## About WorkOS FGA | ||
|
||
## Getting Started | ||
|
||
To get started with the Warrant Edge Agent, refer to our documentation on [Setting up the Edge Agent](https://docs.warrant.dev/quickstart/edge-agent). | ||
|
||
## About Warrant | ||
|
||
[Warrant](https://warrant.dev) provides APIs and infrastructure for implementing authorization and access control. Check out our [docs](https://docs.warrant.dev) to learn more. | ||
[WorkOS FGA](https://workos.com/fine-grained-authorization) is a managed, centralized, fine-grained authorization service. Check out our [docs](https://workos.com/docs/fga) to learn more. |