LLM Application Development Services

Description

We have a working prototype — a Streamlit app one of our data scientists built — that does something genuinely useful with our claims data, and about forty people now depend on it. It has no auth, no tests, one hard-coded API key, and it falls over roughly weekly. The job is turning it into something we can run. Proper authentication against our identity provider, secrets out of the source, a real database instead of the pickle files, tests around the core logic, and deployment that does not involve someone's laptop. Keep the behaviour. The users like it, and a rewrite that changes what it does while making it robust will fail on adoption even if it succeeds technically.

• Preserve current behaviour while replacing the infrastructure underneath it
• Add SSO against our identity provider with role-based access
• Move secrets into managed storage and rotate the exposed key
• Replace pickle-file persistence with a proper database, migrating existing state
• Add test coverage on the core logic and set up CI and deployment

• Production deployment with SSO and role-based access
• Secrets management with the exposed credential rotated
• Database migration from the existing files
• Test suite, CI pipeline and operational runbook