Encrypted credentials
Store project API keys, passcodes, and tokens encrypted.
Keep project credentials organized and controlled
Manage project keys and tokens with encryption, versioning, auditing, and Workers sync.
Each project has its own environments and its own AES-256 data key, wrapped by a master key held only as a Worker secret. Values can be references to a secret in another project, every change keeps a version that can be revealed or restored, and Compare shows drift between environments without decrypting. Scoped service tokens read one environment over /api/v1 for CI and .dev.vars, and sync targets push changed keys to Cloudflare Workers. Every unlock, reveal, export, token read and sync is audited. The public inventory exposes only random project IDs. Per domain: secret.<domain> holds one domain's secrets only (78 of 79 domains; timeslotx.com is not connected yet).
What Secrets does for you.
Store project API keys, passcodes, and tokens encrypted.
Keep version and audit context for project secrets.
Sync secrets to Cloudflare Workers.
A suggested path for Secrets. What you can do depends on your access in the app.
Identify the key, passcode, or token you need to review.
Review the available version and audit context.
Check the intended Cloudflare Workers synchronization.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each project has its own environments and its own AES-256 data key, wrapped by a master key held only as a Worker secret. Values can be references to a secret in another project, every change keeps a version that can be revealed or restored, and Compare shows drift between environments without decrypting. Scoped service tokens read one environment over /api/v1 for CI and .dev.vars, and sync targets push changed keys to Cloudflare Workers. Every unlock, reveal, export, token read and sync is audited. The public inventory exposes only random project IDs. Per domain: secret.<domain> holds one domain's secrets only (78 of 79 domains; timeslotx.com is not connected yet).
Non-sensitive runtime configuration stays in each Worker's vars; user identity and sign-in stay in Auth.
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
secrets.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.