Production-ready Windows desktop applications, utility software, and specialized tools — built, packaged, and shipped. Not prototype demos. Actual software people download and use daily.
These aren't concept projects — they're live applications with GitHub releases, versioned builds, and real users.
AI Upscaling Tool
AI-powered video upscaling and enhancement pipeline for Windows. Multi-stage processing with GPU acceleration and batch mode.
View Product Page
Ranked Video App
Local-first ranked video production for Windows — clips, captions, overlays, and FFmpeg export without hosted compute.
View Product Page
Windows Utility
Per-monitor OLED protection system with tray-first design, idle detection modes, and persistent settings that survive restarts.
View Product Page
Batch Video Tool
Batch clip selection, FFmpeg processing, and export automation — hours of manual editing collapsed into a single run.
View Product Page
Shipped app PixelForge AI
Not a concept mockup — a packaged desktop app with batch mode, stage controls, and FFmpeg-backed processing. The GUI is the product users download from GitHub Releases.
Shipped app Display Control+
Per-monitor idle rules, overlay modes, and persistent AppData config — distributed as an Inno Setup installer with ongoing versioned releases.
The four product pages above cover features. This is the packaging and distribution reality behind each one.
Ships as a packaged Windows build with a bundled Python runtime and bundled FFmpeg/ffprobe — nothing else to install. A source-mode fallback exists for Python 3.12 users who want to run it directly. Optional narration, credit billing, and email recovery are configurable add-ons, not requirements.
Distributed as an Inno Setup installer plus portable release binaries that must stay in the same folder. Licensing moved from one-time hour packs to a 14-day free trial followed by an annual subscription or lifetime license, with hosted account restore via a recovery code.
A portable PyInstaller .exe with bundled FFmpeg, intro, and music folders that ship together. The executable isn’t code-signed yet, so each release publishes a SHA256 checksum alongside the download for verification.
Desktop tools can include workflow automation — batch pipelines, AI processing stages, scheduled operations, and API orchestration — without moving product UX to the generic automation services page.
From first prototype to distributable release — the full software development lifecycle handled in one engagement.
Python-based desktop applications with Tkinter, PyQt, or custom UI frameworks. Tray integration, background services, multi-window support, and system-level access.
Self-contained EXE builds with PyInstaller — no Python install required on the end user's machine. Single-file or folder builds depending on app architecture.
Versioned releases with changelog, tagged builds, and asset uploads to GitHub Releases. Direct download links for end users without needing a separate distribution platform.
Professional Windows installer with Inno Setup — Start Menu shortcuts, APPDATA config storage, uninstaller, and optional silent install mode for enterprise deployment.
Apps built with version-checking and GitHub Releases polling so users can be notified of new versions without requiring a separate update service.
README, CHANGELOG, build commands, and architecture notes — so you understand the project and can hand it to another developer if needed without starting over.
Which packaging format fits depends on how the app is used day to day — a tray-first utility has different needs than a batch-processing tool.
One self-contained executable, best for portable batch tools that don’t need a Start Menu presence or persistent background service.
A companion-folder layout for apps that bundle FFmpeg, media assets, or other runtime dependencies the executable needs to find at launch.
For apps meant to run continuously in the background — Start Menu shortcuts, AppData config storage, and a proper uninstaller.
Every build ships as a tagged release with changelog notes, so users and the auto-update check both know exactly what changed and when.
Executables without a paid code-signing certificate still ship a SHA256 checksum in the release notes, so anyone can verify a download before running it.
Apps poll their own GitHub Releases feed and surface an update banner instead of requiring a separate update service or manual version checking.
A deliberate path from working prototype to a distributable, maintainable application.
Define what the app does, what it doesn't do, and what "shipped" means — before a prototype is built.
Minimal working build to validate core functionality. Fast to make, fast to throw away if the approach is wrong.
Error handling, config persistence, tray/installer integration, and edge case coverage added before packaging.
PyInstaller build, installer generation, and clean-install testing on a fresh Windows environment to catch dependency issues.
GitHub Release tagged, asset uploaded, README and CHANGELOG updated. Ready to share or distribute publicly.
Common questions from businesses before commissioning a custom Windows application.
Simple single-purpose Windows tools start in the mid four figures. Applications with databases, multi-user access, installer packaging, and auto-update systems run higher. A scoped quote is provided after a discovery call — no surprises.
Python with PyInstaller for Windows executables, Flask or Electron for hybrid desktop-web apps, and PowerShell for system-level automation tools. The stack is chosen for reliability and maintainability — not trend chasing.
Yes, if that's a requirement. Offline-capable apps with local SQLite or file-based storage are a core strength of custom executables versus web apps. Internet connectivity can be optional or required depending on what the app does.
Yes. Builds are packaged with Inno Setup into a standard installer (.exe) that can be distributed, deployed via network share, or put on GitHub Releases. Licensing, activation, and auto-update logic can be built in as needed.
Shipped apps here keep getting versioned updates — bug fixes, small features, and stability work — through GitHub Releases with an in-app update check. Ongoing support scope is agreed upfront rather than assumed.
Yes, if it was built with a maintainable structure. Because these apps ship with documentation and versioned source history, adding a feature later doesn’t require rebuilding from scratch.
If you have a workflow that needs a real Windows application — not a web app, not a browser extension, but actual desktop software — let's talk scope. I've shipped real products and know what it takes to get from idea to installer.