DislifySearch for a command to run...
Dislify was built as a real media-compression product for video, image, and audio workflows. The deployed platform includes asynchronous FFmpeg processing, Stripe subscriptions, private Cloudflare R2 storage, developer APIs, a JavaScript/TypeScript media SDK, Google Drive and Dropbox imports, automatic paid-plan share links, signed webhooks, analytics, CMS tooling, operations monitoring, and the surrounding infrastructure required to keep building it as a SaaS.
Asking price
$5,000
This is not a repository-only acquisition. Buyers can use the deployed SaaS, create accounts, run compression jobs, inspect the dashboard, test Stripe billing, exercise developer tooling, and review the worker infrastructure before discussing diligence and handoff.
Included in the acquisition
For 30 days following the acquisition, we will provide developer and technical support for the transferred Dislify platform, including handoff assistance, deployment questions, troubleshooting, and fixes for any bugs discovered in the existing codebase.
This support covers the product as transferred and does not include new feature development, redesigns, custom integrations, or other product expansion.
Next.js, TypeScript, Prisma/PostgreSQL, Better Auth, dashboards, account management, subscriptions, notifications, SEO, and production-ready public pages.
Uploads become persistent jobs processed asynchronously through FastAPI, Redis, Celery, and FFmpeg instead of keeping a browser request open.
Checkout, subscriptions, upgrades, scheduled downgrades, customer billing flows, plan synchronization, and Stripe webhooks are already connected.
Scoped API keys, REST compression endpoints, the @dislify/sdk media client, usage tracking, quotas, signed webhooks, and developer documentation.
Google Drive and Dropbox can import supported media directly into Dislify's private processing pipeline without a browser-side re-upload.
Protected worker telemetry covers CPU, memory, disk, Celery workers and queues, Redis, R2 connectivity, cache usage, and cleanup operations.
Database-backed blog and documentation systems provide publishing, categories, tags, media, comments, SEO metadata, and product documentation.
For someone looking for a SaaS business for sale, a ready-made media compression SaaS, or an established Next.js project they can rebrand and continue developing, Dislify provides the product, processing stack, billing, storage, developer tooling, content systems, and administration layer without requiring a new build from scratch.
Why Dislify is available
Dislify was not created as a quick template or a project built purely for resale. We developed it as an operating media-compression SaaS and continued expanding the product, infrastructure, billing, developer tooling, content systems, and operations layer.
Dislify was developed as a functioning SaaS rather than a codebase assembled specifically for an acquisition listing. The live application, worker infrastructure, customer accounts, billing flows, APIs, storage, analytics, and administration systems were built to work together as one product.
As our time and attention have shifted toward other products, continuing to divide development time across every project no longer makes sense. Rather than leave Dislify without the focus required to keep growing it, we decided to make the platform available to a new owner.
A buyer can take over an already-deployed product, keep the Dislify direction or rebrand it, change pricing and positioning, add features, market it to new audiences, and continue building on infrastructure that is already in place.
The sale is therefore a decision about product focus, not an attempt to unload a broken or unfinished application. Buyers can test the deployed platform and inspect the systems described on this page before moving into deeper diligence.
Processing architecture
Dislify separates uploads, job state, processing, storage, and delivery. Once a job is accepted, Redis and Celery coordinate the worker while the web application remains available for other requests.
The source file is accepted and stored.
A persistent compression job enters Redis.
Celery and FFmpeg process the media independently.
The output reaches private R2 and becomes downloadable.
Users do not need to keep an HTTP request or browser tab open while a large file is being processed. Progress, results, retries, and failures are stored as persistent application state.
Operational depth
Dislify includes the tooling needed to understand what the worker stack is doing instead of treating background processing as a black box.
Compression jobs are queued in Redis and executed by Celery workers using FFmpeg. Processing continues independently from the browser.
Inspect CPU, RAM, disk usage, queue depth, active tasks, worker count, Redis state, R2 connectivity, process information, and service health.
Private Cloudflare R2 storage, signed uploads and downloads, separate source and output objects, expiration-aware delivery, and automated cleanup.
Users can track progress, inspect history, download results, retry failed jobs, recompress files, and review compression savings.
Pro and Unlimited jobs automatically receive public share links after completion, with owner-controlled expiration that never outlives stored output retention.
Database-backed notifications cover jobs, billing changes, API keys, webhooks, quota limits, and account activity.
Resend can notify signed-in users when long-running compression jobs complete or fail, so they do not need to keep the application open.
What is already built
For buyers comparing SaaS projects for sale or ready-made software businesses, Dislify includes the major systems required to operate a media compression product across customers, billing, processing, storage, APIs, content, analytics, and administration.
The platform is grouped below by responsibility so you can quickly understand what is already implemented and what would transfer as part of the acquisition.
The customer-facing product is already implemented rather than being a landing-page template.
Accounts, paid plans, billing state, and subscription changes are wired into the application.
Media processing runs outside the Next.js web request through a separate worker architecture.
Uploads and processed outputs already use a private object-storage workflow.
Dislify can also be used programmatically by developers and external applications.
The platform records actual application activity rather than displaying placeholder dashboard statistics.
Public content can be managed from the application instead of being hardcoded into source files.
A protected superuser area gives the owner control over the platform and its content.
The acquisition includes more than source code — buyers can inspect and test the operating product.
Built-in operations
The protected worker dashboard gives the owner visibility into the services responsible for processing customer media.
System
CPU · RAM · Disk
Queue
Celery · Redis
Storage
Cache · Cloudflare R2
Maintenance
Cleanup · Scheduling
Buyer inquiry
Your message is stored with the acquisition leads in Dislify's database and the owners receive an email notification when it arrives.