Workforge's answer

Most "free" web tools online aren't really free. You get three uses a day, or a watermark, or a signup wall, or your file gets uploaded to somebody's server so they can train a model on it, not to mention every part of the screen covered in ads. Workforge is the opposite. Every tool runs in your browser, doesn't ask for an email, doesn't stamp a logo on your output, and doesn't send your files anywhere. If a tool can be built to run locally, we build it that way.

warmup.rocks's answer:

Most cache warmers run from one server, so they only warm the one CDN edge location that server happens to hit. CDNs like Cloudflare cache per data center, 300+ of them, and a HIT in Frankfurt says nothing about Singapore.

warmup.rocks is different:

• Warms from 42 countries on 6 continents, so the cache gets filled where your visitors actually are
• Verifies every response (cf-cache-status, x-cache) instead of just firing requests and hoping
• Shows hit ratio per edge location, so you see whether warming actually works
• Nothing to install: no plugin, no script tag, no DNS change

Workforge's answer

Small business owners, freelancers, developers, and anyone who has a job to do and doesn't want a subscription for it. A lot of our early usage is people converting images in bulk, generating one-off invoices, or wrangling data between formats (JSON, CSV, Excel, Markdown). The common thread isn't industry - it's that they need a utility, not a SaaS relationship. If we can build and run it for little/no cost, we don't charge for it, and if we have to charge for it, we charge a fair price that is typically a lot better than the larger companies.

warmup.rocks's answer:

Developers, agencies and store owners who run sites behind a CDN (Cloudflare, Fastly, CloudFront, Akamai, bunny.net) and serve visitors in more than one region. Typical cases:

• WordPress/WooCommerce sites where preload plugins stop at the server cache
• Shopify and Magento stores with a long product tail that never stays warm on its own
• Anyone whose deploys purge the edge cache and leave the first visitor per location with a slow load

Workforge's answer

Next.js and TypeScript for the apps, Tailwind for styling, Supabase (where we legitimately do need backend), and Vercel for hosting. The whole platform is a Turborepo monorepo so each tool ships as its own app on its own subdomain. Wherever possible, the actual work (image processing, file conversion, etc.) happens client-side in the browser so files never touch a server.

warmup.rocks's answer:

• Node.js + TypeScript with Hono as the web framework
• SQLite for storage
• Astro for the public site, vanilla JavaScript for the dashboard
• Warming requests go through dedicated datacenter proxies in 42 countries

The whole thing runs on a plain VPS behind Cloudflare, which keeps it fast and cheap without a pile of infrastructure.

Workforge's answer

No enterprise logos to drop here... yet! We're hoping to change that, but more importantly we're hoping to provide real value to the SMB, Indie & freelancer community. We know what it's like to be a small business, just starting out, when every dollar spent is a tradeoff and we want to help solve that problem.

warmup.rocks's answer:

• this:matters GmbH (the Swiss web agency behind the product, running client sites through it)

Workforge's answer

I've been running businesses for a long time. Every time I needed a simple utility; resize a batch of photos, spit out an invoice, convert a file, the internet handed me the same three options. 1) a "free" site so buried in ads and popups you can barely see the button you came for, and half the time the download is a redirect to something you didn't ask for. 2) Adobe, where reading a PDF is free but anything past that wants a subscription. 3) Canva, charging like it's a premium product for what's honestly a commodity, templates and a drag-and-drop editor dressed up as a platform.

At some point it clicked that none of this stuff is hard. The reason it costs money (or costs you your attention to fifty ads) isn't that the tools are expensive to build. It's that somebody figured out they could charge for it, or monetize your eyeballs while you use it. That's it. That's the whole business model.

So I started building the versions I actually wanted to use. Clean pages, no ads, no signup, no watermark, no "upgrade for full quality." Just the tool. The first few were for me. Then a friend asked if I could do one for something they needed. Then somebody else. After enough of those, it made more sense to just put them online than to keep rebuilding them one-off.

That's Workforge. It's the set of tools I wanted to exist when I was staring at another ad-choked converter or another paywall.

warmup.rocks's answer:

I run a web agency in Switzerland, and for years I believed our sites were fast because we put them behind Cloudflare and saw HIT in the headers. Then I measured from other continents: pages that loaded in milliseconds from Zurich took multiple seconds from Tokyo or São Paulo, because each edge location keeps its own cache and most of them were cold.

I built a warmer for our own client sites first, then measured 408,000 CDN requests and found a miss is 3.5× slower than a hit at the median. That data convinced me this should be a product.

Workforge's answer

No ads. You land on a Workforge tool and it looks like a tool, not a billboard. No popups, no "download" buttons that redirect you somewhere else, no banner ads shifting the layout while you're trying to click. People notice this immediately — it's usually the first thing they compliment.

It's fast. Because the tools run in your browser instead of uploading your files to a server, there's no wait, no queue, no "processing…" spinner while somebody else's backend catches up. You pick a file, it's done.

Nothing to install, nothing to sign up for. Everything works from a browser tab. No account, no email capture, no free trial that turns into a subscription.

Most tools are free, and the ones that aren't stay cheap. The default is free. If a tool ever needs to be paid — because it costs real money to run — it'll be priced like a utility, not like a SaaS product pretending to be something bigger.

Requests actually get built. If you submit a request and say "I wish there was a tool that did X," there's a good chance it shows up on the site within the next few days (within reason...). In fact, that's literally how half the current tools got made. Try that with Adobe.

warmup.rocks's answer:

Three reasons:

• Geography. Competitors warm from a single region. We warm from 42 countries, which is the whole point of a CDN cache.
• Verification. We read the cache status header of every single response and report the actual hit ratio per location, so you see whether warming works instead of taking it on faith.
• Deploy integration. A deploy hook or our GitHub Action re-warms the cache right after you ship, which is exactly when it's coldest.

Plans start at $15/month with a 7-day free trial.