Snapify

Snapify records your screen and hands back a link, which is the entire loop asynchronous video tools exist for. What changes is where the files land, because you run the application and the storage bucket yourself instead of trusting a vendor with footage of internal systems.

Recording covers a browser tab, the whole desktop, or a single application, with no cap on how many you make. Each recording gets a public link, and one can be unlisted or deleted after a chosen timeframe. Video recorded elsewhere uploads into the same library and shares the same way.

Under the hood it is a Next.js application using Prisma against MySQL, NextAuth for login, and object storage for the video files. Self-hosting means assembling a few standard services, each configured through environment variables.

• Database: MySQL reached through Prisma, with the schema pushed by a single command.
• Authentication: NextAuth backed by a GitHub OAuth app you register yourself.
• Object storage: any S3-compatible bucket holds the video, kept private rather than publicly readable.
• Session secret: a generated key signs sessions and has to be set before the first run.
• Hosting: a Vercel deploy button provisions the app with every required variable listed.

The setup guide walks through Railway for the database and Backblaze B2 for the bucket, though the variables are ordinary AWS ones and other providers fit. End to end tests ship with the repository, and the license is AGPLv3, so a modified deployment has to publish its changes.