# Sunsetting a company app without loose ends

Page: https://stenobird.com/podcast/no-compromises-1309932/sunsetting-a-company-app-without-loose-ends
Text version: https://stenobird.com/podcast/no-compromises-1309932/sunsetting-a-company-app-without-loose-ends.md
Podcast: [No Compromises](https://stenobird.com/podcast/no-compromises-1309932)
Published: 2025-09-13T05:00:00+00:00
Episode link: https://share.transistor.fm/s/705481c9
Audio file: https://media.transistor.fm/705481c9/6690307e.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/sunsetting-a-company-app-without-loose-ends
Duration seconds: 835

## Resource

Business change and projects end, but how do you wrap up and sunset an app, especially one you've worked on for years? In the latest episode of the No Compromises podcast, we share a practical checklist for winding down an app when the whole company is closing. From documenting services and dependencies to deciding what data to retain, we cover backups, credentials, and why deleting local copies matters for security and sanity. (00:00) - Sunsetting a company vs project handoff (02:15) - First goals: stop charges, purge data (03:45) - Document before shutting anything off (04:15) - Use README/PRODUCTION.md and password manager (05:45) - Decide on retaining code, DB, uploads (07:15) - Hunt secrets in .gitignore and dotfiles (09:15) - Delete local containers and repos by default (11:30) - Silly bit Want peace of mind that your project is ready for whatever happens in the future. Schedule a call with us today.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/sunsetting-a-company-app-without-loose-ends/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/no-compromises-1309932/sunsetting-a-company-app-without-loose-ends.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.