Architecture

Built to be checked.

Feathergrid connects to the systems you already run, finds what's related, and writes every decision to a tamper-evident record anchored across Azure and AWS. Here's how it fits together, and exactly where we stand.

0Data migrations
2 cloudsAnchor the record
Hashes onlyCross to AWS
1 switchStops everything

From your systems to your next move

Four steps. Each one leaves a trail you can inspect.

  1. 01

    Connect

    Reads from the apps and systems you already run, and sensors if you have them, through their APIs, files and feeds. Your systems stay the source of truth.

  2. 02

    Relate

    Lines events up four ways: same time, same place, one leads to the next, and it's happened before.

  3. 03

    Recommend

    Your rules decide what happens. Routine steps run on their own. Big calls wait for a named approver. Alerts go out by text and email.

  4. 04

    Record

    What it saw, what it recommended, who approved it and what happened next go into the record.

A record no one can quietly change.

Most software keeps its history in one database. Anyone with enough access can edit it, and nobody would know. Feathergrid anchors its record across two clouds run by two different companies.

  • Every entry gets a fingerprint. A short code calculated from the entry. Change one character and the code changes.

  • The fingerprints live somewhere else. They are anchored on AWS, outside the cloud that runs the app.

  • Edits show. Change history in one cloud and it stops matching the other.

  • Your data stays in one place. Only fingerprints cross to AWS, which keeps the compliance boundary small.

  • Heals itself. If the record and the ledger are in conflict, Feathergrid triggers a rollback to the backup database.

Your data stays where it is.

Feathergrid goes to your systems. Your systems don't come to us.

  • No migration. Feathergrid connects to your systems where they are. Nothing gets replaced.

  • Runs on Azure. The app and your data in one cloud. Only fingerprints leave it.

  • Not used to train AI models. Your data does its job for you and nobody else.

  • Need it in your own cloud? Ask us. We'll tell you exactly what's ready.

How it's put together

For the engineers. Small, independent pieces, so nothing has to stop for one part to change.

Event log first

Every change is an event. The log is the source of truth.

Memory-first cells

Each cell keeps its working set in memory, close to the data it serves.

No central coordinator

Cells share state with each other directly, so there's no single point to fail.

Compute goes to the data

Queries run where the data lives instead of copying it out.

Locality-aware routing

Consistent hashing sends each request to the cell that owns it.

Rolling upgrades

Cells update one at a time. The system stays up.

C4 Model

Architecture at every level

From the outside in. Click any box to see what it does. Boxes marked "drill in" open the next level.

Level 1 · Context
5 elements · 4 relationships
«Person»Your team«System»Feathergrid[Platform]drill in →«External System»Microsoft Azure[Ready]«External System»Amazon Web Services[Ready]«External System»Edge[Ready]
PersonSystemExternalContainerComponentDashed line = async

Select any element

Click a box in the diagram to see what it does and what it connects to.

Current level

Level 1 · Context

Who uses Feathergrid, and where it runs.

Where we stand

Security teams check every claim. So here it is, plainly.

  • FedRAMP

    Not authorized today. Built to run inside a partner's authorized environment.

  • Been through the audit

    Our founder has taken architectures through HIPAA and FedRAMP High audits.

  • Your data stays in the US

    Processed on Azure in the US. Never used to train AI models.

  • Everything else

    Ask what we hold today. If we don't have it, we'll say so.

Questions

Does Feathergrid require a data migration?

No. Feathergrid connects to the systems you already run. Your systems stay the source of truth.

What does tamper-evident mean for Feathergrid?

Every entry in Feathergrid's record gets a cryptographic fingerprint. The fingerprints are anchored on AWS, outside the Azure cloud that runs the app. If an entry is changed, it no longer matches its fingerprint.

What data goes to AWS?

Only fingerprints. No application code and no customer data.

Is Feathergrid FedRAMP authorized?

Not today. Our founder has taken architectures through HIPAA and FedRAMP High audits.

Skeptical? Good.

Bring your hardest questions. We'll walk your team through the architecture and show you what's running today.