Are you sure you want to delete this access key?
title | description | authors | tags | keywords | date | image | imageAlt |
---|---|---|---|---|---|---|---|
System Cards Go Hard | Master LLM system cards for responsible AI deployment with transparency, safety documentation, and compliance requirements | [tabs] | [research-analysis best-practices openai anthropic] | [llm system card AI safety documentation model transparency responsible AI] | 2025-07-15 | /img/blog/system-cards-hero.jpg | Illustration of LLM system cards timeline 2022-2025 |
A system card accompanies a LLM release with system-level information about the model's deployment.
A system card is not to be confused with a model card, which conveys information about the model itself. Hooray for being given far more than a list of features and inadequate documentation along with the expectation of churning out a working implementation of some tool by the end of the week.
The first system card possibly came about from Dalle-2 in 2022, although Meta researchers were using the term earlier. OpenAI started publishing them in March 2023 (GPT-4). Anthropic followed suit. If there are other models with accompanying system cards, let me know. I'd love to sit down and spend three hours sifting through 169 pages of some LLM I don't use.
The following list isn't comprehensive or indicative of all models. Information can span:
Anyone concerned about the security of their applications would find this a fantastic place to learn about the quirks of using LLMs and responsible AI practices the companies producing them employ. This is information we can use to educate our users, inform our own deployment practices, and introduce the necessary precautions for interactions with the LLMs concerned.
They are invaluable... And admittedly, interesting.
These are the system cards I could find:
Evolution of system card releases
Common evaluation categories in system cards
OpenAI's GPT4o
Anthropic's Claude 4 Opus and Sonnet
(Not gonna lie - Anthropic's system card contained WAY more useful information.)
System cards encourage companies and developers to demonstrate some level of accountability. I imagine they'd be useful for anyone deploying an LLM themselves. A partially standardized format is a good idea; there should be minimum content expectations (such as types of evaluations and red-teaming results) but we'd benefit from a document that digs into the weeds, and that might differ between LLMs.
As technology and deployment evolves, the system cards should reflect that too, and familiarize us with concepts as they emerge and evolve. The insight and novelty will encourage more people to read them.
I'll leave you with a terrible haiku I wrote:
Read system cards to Avoid the ultimate pain: LLM hubris.
Press p or to see the previous file or, n or to see the next file
Browsing data directories saved to S3 is possible with DAGsHub. Let's configure your repository to easily display your data in the context of any commit!
promptfoo is now integrated with AWS S3!
Are you sure you want to delete this access key?
Browsing data directories saved to Google Cloud Storage is possible with DAGsHub. Let's configure your repository to easily display your data in the context of any commit!
promptfoo is now integrated with Google Cloud Storage!
Are you sure you want to delete this access key?
Browsing data directories saved to Azure Cloud Storage is possible with DAGsHub. Let's configure your repository to easily display your data in the context of any commit!
promptfoo is now integrated with Azure Cloud Storage!
Are you sure you want to delete this access key?
Browsing data directories saved to S3 compatible storage is possible with DAGsHub. Let's configure your repository to easily display your data in the context of any commit!
promptfoo is now integrated with your S3 compatible storage!
Are you sure you want to delete this access key?