About Faceless Desk

Faceless Desk covers the tooling behind faceless video production — scripting, AI voice, screen capture, editing and publishing. It exists because we are building a faceless video operation ourselves and kept running into the same problem: the questions that actually decide whether the format works are the ones nobody answers straight.

Who writes this

Faceless Desk is written by Branislav, working alone — not a media company, not an agency. There is no editorial team, no sponsor list and no client whose product needs a good review. That is worth knowing in both directions: it means nobody is paying us to reach a conclusion, and it means this is one person's research rather than a newsroom's.

The site is part of LinkLoom, a small portfolio of properties that also builds the click-tracking infrastructure every outbound link here runs through. We mention that because it explains the go.linkloom.dev links you will see — that redirect is ours, not a third-party tracker.

How the research works

Every article states its basis at the top, using one of three labels, and we would rather publish an honest research-led than pretend to hands-on experience we do not have:

• Used daily — a tool in our actual production workflow.
• Hands-on trial — genuinely used, but not at volume.
• Research-led — built from vendor documentation and platform policy, not from running the thing ourselves.

Being straight about where that currently stands: all 22 guides published so far are research-led. The site is new, and what is here was built by reading vendor documentation and platform policy closely rather than by running each tool at volume. That is genuinely useful for questions about licensing, pricing and platform rules — which is most of what is covered — and it is not the same as having used everything. As tools move into daily production use, those articles get relabelled and this number changes on its own.

What we hold ourselves to

• Cite the primary source. Platform rules and pricing come from the vendor's own documentation, linked at the foot of each article. Where only third-party reporting exists, we label it as such.
• Say when we do not know. Several articles here end by stating that a widely repeated "fact" cannot be sourced. That is a more useful answer than a confident guess, and it is the failure mode most tool-review content has.
• Show the arithmetic. Cost claims come with the assumptions that produced them, so you can redo the sums against your own numbers instead of trusting ours.
• Name the free option when it wins. It frequently does, and several articles here recommend spending nothing.
• Never buy a product to review it — and never pretend otherwise. The tools covered are ones a faceless operation genuinely uses, with free tiers and trials doing the work that a purchase would otherwise require.

How this is funded

Some links earn a commission if you subscribe, at no extra cost to you. Pages carrying a commissioned link say so on that page — the notice is generated from whether the link actually earns, so it cannot drift out of sync in either direction. Pages without one carry no disclosure because there is nothing to disclose.

We are not paid for coverage, placement or a rating. No vendor has been given review approval, and none has seen an article before publication. Where we have not been accepted into a programme, the tool still gets covered and the link simply earns nothing — which is the situation for most tools mentioned here today.

The privacy policy explains exactly what the outbound redirect records, which is deliberately close to nothing: no IP addresses, no cookies.

Corrections

Vendor pricing and platform policy change without notice, and some of what is here will go stale. If you find something wrong or out of date, tell us at [email protected] and it gets fixed with the change noted, rather than quietly edited.