Your own keys and connections, sealed and verifiable.
In plain words: Your own API keys and connections, sealed.
Operations · No PHI · Every specialtyBring your own accounts — your model provider, your Resend domain, your payment gateway, your WhatsApp number, your own Supabase project — and the platform uses them instead of ours. Each key is sealed under a data key that is itself sealed under the deployment master key, and bound to your organisation so a copied row opens nowhere else. Stored keys are checked against the provider on the spot, so a wrong key is wrong at the moment you paste it rather than at 2am.
It never shows a key back. Once stored, a secret is only ever a masked hint — not to you, not to us, not to support. There is no reveal endpoint to be talked into.
Every app page carries this section. A listing with only benefits is an advertisement.KeyRing reads nothing — it holds credentials, not records and writes sealed credentials, verification outcomes. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.
It never shows a key back. Once stored, a secret is only ever a masked hint — not to you, not to us, not to support. There is no reveal endpoint to be talked into.
Revoked keys stop being used immediately; the rows stay so an incident can still ask which key was in force last month.
Yes — KeyRing is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.