About

Independent. Focused. Useful.

Every project here is built and maintained independently, with a focus on clean code and practical workflows that solve real problems.

6Articles
6Tools
6Products
631Reads
The story
F FilmorexBuilt independently, one release at a time.
“

Build small things that do one job extremely well - write down what you learned, and give the useful parts away for free.

Filmorex - operating principle
The story

Why this site exists

Most writing about AI and software building falls into two traps: shallow listicles written for search engines, or giant vendor pitches dressed up as tutorials. Neither helps when you are actually trying to ship something. Filmorex was built to be the third option - notes from real work, written by the person who did the work.

The format is deliberately small. Articles appear only after the approach has been built and broken for real, so every guide includes the trade-offs, the dead ends and the parts that failed. The free tools exist because the same problems kept coming up in projects - instead of googling yet another ad-heavy converter, they live here, running privately in your browser. The products are where ideas graduate when they prove worth maintaining.

There is no team of twenty behind this, no sponsor writing the roadmap and no ad network deciding what the layout looks like. The readers are the audience, not the product. Everything core - the articles, the tools, the series - stays free, untracked and without login walls. If that sounds like the kind of place worth returning to, start with the latest articles or the free tools.

Inside the site

What you will find here

Articles, guides, free tools and small products - all built around AI, engineering, automation and independent product building.

Engineering notes

Real implementation details, trade-offs and post-mortems - not tutorial fluff.

Free tools

Browser-first utilities that respect your time, data and bandwidth.

Shipping products

Small, focused products launched in public and improved with user feedback.

const filmorex = {
  focus: ["AI", "engineering", "automation"],
  articles: 6,
  tools: 6,
  products: 6,
  shipped: true
};

6

Articles

6

Tools

6

Products

By the numbers

The site, in real time

Live counts pulled straight from the database - not marketing round numbers.

6 Articles
731 Words written
631 Reads
4 / 2 Categories / Series
12 Tools + Products
Process

How an article gets made

No content calendar, no ghost-written filler. This is the actual path from idea to published page.

1

A real problem

Ideas come from work that was actually being done - a bug, a refactor, a workflow that kept wasting time. Never from keyword research.

2

Build and break it

The approach is implemented and pushed until it holds up - edge cases, failure modes and limits get mapped before anything is written.

3

Write the hard parts

The article focuses on trade-offs, mistakes and the parts readers usually get stuck on - the easy steps get compressed, not padded.

4

Ship and maintain

Published, then kept honest: corrections land when something changes and outdated sections get updated instead of quietly rotting.

How we work

Six principles behind everything here

Useful over impressive

Every article and tool must solve a real problem. No filler posts, no vanity features.

Independent by default

No sponsors dictate the roadmap. Projects are chosen because they are worth building.

Shipped and iterated

Things go live early, then improve with real feedback instead of endless private polishing.

Honest about limits

Code examples are illustrative, ideas are labelled as rough when they are. No pretending.

Privacy by default

No trackers, no ads, no accounts for readers. Tools process everything on your device.

Free core, always

Articles, series and tools never move behind a paywall. Products may charge; the library will not.

Audience

Who this is for

Written for people who build things - not for procurement pages or resume collectors.

Working developers

Patterns and snippets you can paste into real projects, with the why spelled out.

Indie hackers & founders

Building, launching and distributing small products without a marketing team.

AI-curious builders

Practical workflows that work today - not roadmaps about models arriving in 2030.

Automation tinkerers

Scripts, integrations and small utilities that delete repetitive work from the week.

The workshop

Free tools, straight from real projects

Each tool started as something needed during actual work. All of them run locally in your browser - nothing you process gets uploaded.

Open all 6 tools

FAQ

Good to know

What exactly is this site?
A mixed workspace: a blog with practical AI and engineering write-ups, a set of free browser tools, and a small suite of independently built products - all maintained under one roof.
Is the content and are the tools free?
Yes. Every article is open to read and every tool listed under Tools is free to use - no accounts, no paywalls, no email gates. The free core stays free by principle.
Do you track visitors or run ads?
No. There are no advertising scripts, no third-party analytics and no tracking cookies. The tools process your files and text on your own device. The full details live in the Privacy Policy.
Are the tools safe with sensitive data?
The tools run entirely in your browser - text, JSON and images you load are never transmitted to the server. That said, always use your own judgement with truly sensitive material and keep private work on machines you trust.
Can I suggest a tool or an article topic?
Please do. Tool ideas, article requests, bug reports and corrections all go through the contact page and get read by the same person who builds things here.
Do you accept sponsored posts or guest articles?
Sponsored articles are not published here. The roadmap is set by what is genuinely useful to build and write about, not by paid placements. Collaboration ideas are still welcome through the contact page.
Can I reuse your articles elsewhere?
Quoting short excerpts with a link back is fine and encouraged. Republishing full articles - in newsletters, aggregators, courses or books - needs permission first. The rules are spelled out in the Terms of Service.
How often do you publish?
There is no fixed calendar. Posts ship when something is genuinely worth writing up - quality and accuracy over hitting a quota. Series are the right place if you prefer a structured run of connected parts.
How do I get in touch or suggest something?
Use the contact page - tool ideas, bug reports, corrections and project enquiries all go to the same inbox and get read.
In writing

About

Filmorex is written and maintained by one person - the same person who builds the tools and products on this site. There is no editorial team, no outsourcing and no content agency. When an article appears, it is because someone here solved a problem and took the time to write the solution down properly.

The work sits at the intersection of four interests: artificial intelligence used as a daily working tool rather than a headline, software engineering with all its trade-offs intact, automation that removes repetitive work, and independent product building - the craft of shipping small things that pay for themselves.

Everything public here follows one rule: if it would not be useful to the person who built it, it does not get published. That means fewer posts, longer lifetimes for each one, and a standing invitation to point out anything that is wrong - corrections are treated as gifts, not embarrassments.

The site has no investors to answer to and no growth targets to hit. Success looks like a reader leaving with something they can use the same day, and a slow, steady library of pages that are still worth reading years later.

Say hello

Want to work together?

Have a project, a question or a tool idea? Send a message and let us talk.