Tag: infrastructure
All the articles with the tag "infrastructure".
-
How This Site Is Built
Updated:The stack behind artificialcuriositylabs.ai: Astro on S3 + CloudFront, DNS on Cloudflare, email forwarding via SES, and an AI-readable content layer. Every decision explained.
-
The Pareto Frontier Is the Model Market Map
Model leaderboards tell you who is smartest. The Pareto frontier tells you which models are still rational choices once price enters the room.
-
When the Tool Doesn't Know About the Vault
op run wraps any process and resolves vault references as normal env vars — so the tool reads credentials without knowing 1Password exists.
-
The Same Pattern, From Solo Builder to Enterprise Scale
The credential pattern in this series works for one person today. It also works for a team of ten, or a company of ten thousand. The vault-and-IdP architecture doesn't change when you add users. That's the point.
-
1Password as the Trust Anchor for an Agent Auth Chain
The previous posts covered what 1Password stores. This one is about what it does — as the live trust anchor when an agent acquires tokens, enrolls MFA, and calls protected APIs without a human passing credentials by hand.
-
What Happens When an AI Agent Manages Your Password Vault
I used Claude Code and the 1Password CLI to reorganize 690 credentials — four vaults, 400+ tagged items, a GitHub issue filed from the terminal. Here's what worked, what broke, and what it means for AI-native credential management.
-
1Password Is Infrastructure, Not a Password Manager
1Password just announced credential infrastructure for AI agents. The pattern already works today — personal account, existing CLI, GitHub Actions pulling exactly the credentials each workflow needs from a vault scoped to its purpose. Here's what that looks like and why it matters.
-
The Builder Stack Nobody Told You 1Password Covers
1Password gets described as a password manager. It also replaces SSH key files, GPG for git signing, .env files, AWS credential storage, and scattered Secrets Manager entries — all from one vault, all behind a single biometric prompt.