Fabric finds assets by their rights and flags current versus superseded, so you can tell which version legal actually cleared. Forge returns generated images with visible watermarking and C2PA Content Credentials carrying an AI-source assertion. Gateway puts an audit row on every question. No migration, no new silo, just a clear answer when someone asks.
Fabric finds assets by their rights and flags current versus superseded, with permissions enforced inside the query itself. You can tell at a glance whether a file is the version legal cleared, not last quarter's lookalike or an expired license.
Forge returns generated output with visible watermarking on video, image and document, and C2PA Content Credentials on images carrying an AI-source assertion. When legal asks where an asset came from, the answer travels with the file.
Gateway resolves permissions per question and writes a severity-tagged audit row on every one, exportable to your SIEM. You stop reconstructing who saw and pulled what from folder timestamps and memory.
A SOC 2 Type II aligned engineering posture, designed for MPA content-security best practices. That is engineering discipline, not third-party certification, and it comes with SSO over OIDC and SAML 2.0, authenticator-app MFA and role-based access.
Book the ones that fit your team, or the whole platform. Each shares one index.
Find assets by their rights and see current versus superseded before anything ships. Permissions and version time-awareness live inside the query, so a search only surfaces what a person is cleared to see and flags the expired, the retired and the superseded instead of quietly returning them.
Every processed or generated output carries visible watermarking on video, image and document, and images carry C2PA Content Credentials with an AI-source assertion. When brand or legal asks whether an asset is generated and where it came from, the provenance is baked into the file, not bolted on after the fact.
Permissions resolved per question and a severity-tagged audit row on every query, exportable to your SIEM. Read-only by design, so a question can never change your data, and you can produce a complete trail of who asked for what when legal or an auditor comes calling.
Marketing wants a hero image out today. You ask Fabric for the asset by its rights and it flags current versus superseded, with permissions resolved in the query, so you approve the version that was actually cleared and not an expired or retired lookalike.
The team needs a fresh variant. Forge generates it inside your permissions and returns it with visible watermarking plus C2PA Content Credentials on images carrying an AI-source assertion, so a generated asset is traceable the moment it exists instead of becoming an unlabeled mystery later.
A rights question comes back weeks later. Gateway shows a severity-tagged audit row on every query, exportable to your SIEM, so you answer who pulled what and when with a record, not a reconstruction from folder timestamps.
Fabric finds assets by their rights and flags current versus superseded, with permissions and version time-awareness enforced inside the query itself. So when marketing asks to ship a still or a cut, you can tell at a glance whether it is the version legal actually cleared, rather than an expired license or a superseded lookalike, before it goes out the door.
Yes. Forge returns generated images with C2PA Content Credentials carrying an AI-source assertion, and applies visible watermarking on video, image and document outputs. The provenance travels with the file, so when legal or a partner asks whether an asset is AI-generated and how it was made, the answer is embedded in the asset instead of living in someone's memory.
Gateway resolves permissions per question and writes a severity-tagged audit row on every query, which you can export to your own SIEM. It is read-only by design, so a question can never change your data. That gives you a complete, exportable record of who asked for what and when, instead of reconstructing access from folder timestamps after the fact.
No, and we do not claim to be. Asset Foundry is built to a SOC 2 Type II aligned engineering posture and designed for MPA content-security best practices, which describe engineering discipline rather than third-party certification. That posture includes SSO over OIDC and SAML 2.0, authenticator-app MFA, role-based access and severity-tagged audit logging you can export. The fastest way to see it against your own library is the four-week pilot: one slice, read-only, findings in your numbers.