# Looking for feedback: encrypted credentials workflow for Django

**URL:** <https://forum.djangoproject.com/t/looking-for-feedback-encrypted-credentials-workflow-for-django/45296>\
**Category:** Show & Tell\
**Created:** [June 14, 2026, 11:45pm UTC](https://forum.djangoproject.com/t/looking-for-feedback-encrypted-credentials-workflow-for-django/45296 "2026-06-14T23:45:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lexpank](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/lexpank/32/32641_2.png) [@lexpank](https://forum.djangoproject.com/u/lexpank)\
**Post date:** [June 14, 2026, 11:45pm UTC](https://forum.djangoproject.com/t/looking-for-feedback-encrypted-credentials-workflow-for-django/45296/1 "2026-06-14T23:45:55Z")

</div>

I’ve been working on Secure Credentials Kit, a small package for encrypted, environment-specific credentials in Django (and FastAPI) projects.

The idea is to provide something more structured than plain .env/env.yml files, while staying lighter than a full secrets-management platform. It supports encrypted credential files, a master key for editing, a read-only key for runtime access, Django management commands. It works much like rails credentials

I would appreciate feedback from you guys on the workflow, naming, possible improvements.

Pypi: [https://pypi.org/project/secure-credentials-kit/](https://pypi.org/project/secure-credentials-kit/)