Home
Getting Started
Guides
UI Components
Sign-up & Sign-in
Users
Backend Requests
Welcome to Shieldflow Docs
Learn how to secure everything from staging environments to SaaS apps with Zero Trust principles that are easy to use and administer.
Quickstarts & Tutorials
Explore our end-to-end tutorials and getting started guides for different application stacks using Shieldflow.
UI Components
Shieldflow's pre-built UI components give you a beautiful, fully-functional user management experience in minutes.
API Reference
Dig into our API reference documentation and SDKs. We have everything you need to get started setting up authentication with Shieldflow.
How Shieldflow Works
Shieldflow was designed from the ground up with a strong emphasis on security. One of its key features is that no single component has the authority to independently allow traffic to flow to another component or a Resource in your remote networks. Authorization for user access or data flow is always confirmed by at least two, and sometimes even three, components depending on the sensitivity of the decision. By delegating user authentication to a third-party Identity Provider (IdP), this separation of concerns is further reinforced, adding an extra layer of security to your Shieldflow network.
This guide begins by exploring Shieldflow’s architecture and then delves into how Shieldflow encrypts traffic and ensures that users can securely access only the Resources they are authorized to use.
Shieldflow relies on four core components—Controller, Clients, Connectors, and Relays—to ensure that only authenticated users can access the designated Resources. These components work together to create a secure and controlled access process.
Shieldflow was designed from the ground up with a strong emphasis on security. One of its key features is that no single component has the authority to independently allow traffic to flow to another component or a Resource in your remote networks. Authorization for user access or data flow is always confirmed by at least two, and sometimes even three, components depending on the sensitivity of the decision. By delegating user authentication to a third-party Identity Provider (IdP), this separation of concerns is further reinforced, adding an extra layer of security to your Shieldflow network.
This guide begins by exploring Shieldflow’s architecture and then delves into how Shieldflow encrypts traffic and ensures that users can securely access only the Resources they are authorized to use.
Shieldflow relies on four core components—Controller, Clients, Connectors, and Relays—to ensure that only authenticated users can access the designated Resources. These components work together to create a secure and controlled access process.
Shieldflow was designed from the ground up with a strong emphasis on security. One of its key features is that no single component has the authority to independently allow traffic to flow to another component or a Resource in your remote networks. Authorization for user access or data flow is always confirmed by at least two, and sometimes even three, components depending on the sensitivity of the decision. By delegating user authentication to a third-party Identity Provider (IdP), this separation of concerns is further reinforced, adding an extra layer of security to your Shieldflow network.
This guide begins by exploring Shieldflow’s architecture and then delves into how Shieldflow encrypts traffic and ensures that users can securely access only the Resources they are authorized to use.
Shieldflow relies on four core components—Controller, Clients, Connectors, and Relays—to ensure that only authenticated users can access the designated Resources. These components work together to create a secure and controlled access process.