Feathergrid for Microsoft Azure Shops: What Fits, and How
If your organization runs on Microsoft Azure, Feathergrid is already at home there. Here is what that means for where your data lives, how keys are held, who can see what, and how enterprise customers run it in their own cloud.
Feathergrid runs on Microsoft Azure. The application and your data live in Azure in the United States, keys are held in Azure Key Vault hardware security modules, and enterprise customers can run Feathergrid in their own cloud. If your organization has standardized on Azure, Feathergrid fits the environment you already have.
Here's what your IT and security teams will want to know.
Where does our data live?
In Microsoft Azure, in the United States.
- Encrypted in transit and at rest.
- Kept separate for each organization.
- Never used to train AI models. Feathergrid's AI works by retrieving the relevant information when it needs it, not by learning from your data.
AWS plays one small part: it holds only the fingerprints that anchor Feathergrid's tamper-evident record. No application code and no customer data. More in Feathergrid on Azure and AWS.
How are keys handled?
Keys are held in Azure Key Vault hardware security modules validated to FIPS 140-3 Level 2. That's the same family of controls many regulated organizations already rely on in Azure.
The application and your data live in Azure in the United States, keys are held in Azure Key Vault hardware security modules, and enterprise customers can run Feathergrid in their own cloud.
Can we run Feathergrid in our own Azure tenancy?
Yes, on the enterprise plan. Feathergrid is deployed as code, with Terraform for the infrastructure and Docker containers for its services, so the same definition that builds our environment can build yours. Your security team can read every change before it's made.
Start with a pilot: 4 to 8 weeks, scoped against your own systems.
Who can see and do what?
Feathergrid uses custom role-based access control. People see only what their role allows, from a single site up to the whole organization.
- Network plans add single sign-on and an organization-wide policy for who may approve what.
- Every plan has the one switch that stops all automated actions, and the tamper-evident record of every recommendation, approval and action.
How does it connect to what we already run?
Through APIs. Feathergrid's connectors are built to connect with APIs, so your data lakes and warehouses, CRMs and applications stay where they are. Feathergrid reads from them and tells you your next move. Sensors on-site connect through a gateway at the edge. See Feathergrid at the Edge.
Where does Feathergrid stand on compliance?
Plainly:
- FedRAMP: not authorized today. Feathergrid is built to run inside a partner's authorized environment.
- Experience: our founder has taken architectures through HIPAA and FedRAMP High audits.
- The record: if the record and the ledger are ever in conflict, Feathergrid triggers a rollback to the backup database.
The government page covers teaming with primes.
The short version
Your data in Azure, in the US. Keys in Key Vault HSMs. Custom roles for who sees what. Terraform and Docker for running it in your own tenancy. And APIs for everything else you already run.
See the architecture page or book a scoping call.
Topics
