Know What Your AI Did
Exactly
Your AI tools are touching company data right now, agents, pipelines, automations, integrations. Do you know what they accessed, and what they did with it?
One line of code
A complete audit trail
Connect IronShard Log to your agent in minutes. From that point forward, every file access, every read, every write is logged automatically, tamper-proof, and exportable.
No infrastructure changes. No custom pipelines. Just answers.
What gets logged
Every query. Every file. Every action, with a timestamp, an agent ID, and a reason when your workflow provides one.
Timestamp
Millisecond-precision UTC on every event, signed at the moment of write.
14:22:11.483ZSource Identity
Every entry is tagged with a named source: an agent, user, script, or service. Know exactly what touched your data.
agent · user · pipelineFile and Path
Full object path for every file accessed, read, written, or queried. Nothing omitted.
/datasets/q1/payroll.csvAction Type
READ, WRITE, DELETE, QUERY, INFER, each action class tagged and filterable.
READ · WRITE · INFERReason Field
If your agent provides a reason for the action, it is captured alongside the event.
reason: "quarterly audit"Export Ready
Every log is structured JSON, exportable on demand for regulators or your own team.
JSON · CSV · PDFBuilt for the question you'll eventually be asked
"Which data did your AI use to make that decision?"
Your regulator. Your client. Your own team.When that question arrives, the answer is already there. Structured, signed, and exportable in one click.
Not just logs
Evidence
IronShard Log records are immutable. They cannot be edited, deleted, or backdated. What happened, happened, and you can prove it.
Written once, sealed immediately
Every entry is cryptographically signed at the moment of write. No window for modification.
sha256: a3f8c9d...Deletion blocked at infrastructure level
Retention policies are enforced below the application layer. No admin override.
policy: immutable_90dChain verification on export
Exported reports include a hash chain so recipients can verify no entries were removed.
integrity: ✓ verifiedStored across IronShard's erasure-coded fabric
Logs are fragmented across providers. No single cloud holds the full record.
6 nodes · 3 providersWorks with whatever your agent runs on
Log attaches to your agent, so it works with whatever framework you build on. Every read, write, and denial it makes against data in IronShard is recorded at the storage layer, whether the agent connects over the S3 API or MCP.