TatteredNote is self-hosted end to end. There's no vendor cloud in the data path, no SaaS backend syncing your incident narratives anywhere — the platform runs entirely on infrastructure you own and control. Controlled data never touches ours.
This describes an architecture posture, not a compliance certification. TatteredNote is designed around self-hosted deployment, record-level classification, and audit logging because those are the right defaults for ITAR/CMMC-adjacent environments — but neither we nor this page can certify your deployment as compliant. That determination is yours to make with qualified export-control counsel, applied to your specific data and configuration. TatteredNote is not designed or authorized for classified information.
Runs on your own infrastructure. No cloud dependency, no vendor-hosted backend in the data path.
Incidents, products, machines, and components can be flagged as controlled technical data. A record about a controlled product or machine is treated as controlled too, and attachments follow the record they belong to. Flagging individual fields within a record is on the roadmap.
Roles decide what someone can do. Separately, an administrator grants each person access to controlled data; for everyone else, controlled records are filtered out server-side — from search, lists, and offline sync. Who qualifies, including U.S.-person status, is your determination; printing a controlled setup packet requires a recorded U.S.-person attestation.
Every view and edit of a record is logged — who, what, when. Nothing is a black box after the fact.
Fix attempts, verifications, outcomes, and votes are write-once: the application refuses to change them after they're recorded. Edits to incident and solution write-ups land in the audit log.
A phone or tablet's offline copy is built through the same access filter as everything else, so it holds only records the signed-in person is allowed to see, and it's wiped when they sign out. Holding offline entries for classification review before anyone else sees them is in development.
Multi-site is on the roadmap, not built. The plan: each facility runs its own local instance, with controlled replication to a hub rather than a single shared database every facility writes into directly. The hub is yours — customer-operated, on your hardware — and replication only ever runs between instances you own.
A facility's data lives on that facility's hardware first. Replication will be deliberate, not a default open pipe between locations.
Shared tag vocabulary and solution ranking will propagate across your hub without forcing every facility onto identical local configuration.
TatteredNote is pre-launch. If your team is evaluating it for a controlled-data environment, we'd rather walk through the actual architecture and your specific data-handling requirements directly than have you infer answers from a marketing page.
Tell us about your environment and what you'd need to see before this could run in it.
Please don't include export-controlled technical data or CUI in the contact form or by email to sales@tatterednote.com. We'll set up the right channel once we talk.
Get in touch