What I do.
I build apps, SaaS, WordPress products and Chrome extensions, and I spend my free hours on GitHub looking for what is really worth it among thousands of repos.
When I find something worth it, I study it, tell it in a short video and give you what you need to try it today: what it is, the key fact, how to start and my verdict. To read and install them I lean on agents like Claude Code or Codex; here I explain which ones and what for.
How I check a repo.
Before a repo appears in a video, I read its README and its official documentation. The facts you see on screen come from there: not from memory and not from what someone said on social media.
- License. I check which license it has and whether it is truly open source or free with conditions.
- Whether it is alive. If it is archived, I say so and tell you what to use instead.
- Warnings. If the README carries a warning, it shows up in the video.
- How to start. Each repo comes with the command or step to try it today, and what you need before you try.
- What I do not do. Use GitHub stars as an argument: they measure fame, not whether the repo is useful to you.
The full method is on the fact sheet and the channel rules, and the checklist to do it yourself is in the 7-step guide. The guide for each repo, with its review date and the source of every fact, is in the repo directory.
What the channel covers, and what it does not.
It covers
- GitHub repos and open-source AI tools you can install and run on your computer.
- Only what you can install today: no “coming soon”.
- Six series: movie-grade repos, stop paying, AI at home, protect yourself, learn for free and program with AI. See the series.
- The license, the warnings and what each thing costs to run.
It does not cover
- Legal, security, financial, tax or technical advice: everything is my opinion and my experience, for information only. Terms (in Spanish).
- A guarantee that a repo is safe, still maintained or right for your case. You confirm that yourself with its current documentation.
- The repos are not mine: they belong to their authors and follow their own license. I do not create or distribute them.
- GitHub stars as an argument, or lab tests I did not run.
I also run SaaS Master.
Since 2019 I make product videos for SaaS, AI and WordPress companies: demos, tutorials, walkthroughs and explainers, in Spanish and English. I write, narrate, record and edit them myself, and the videos belong to the client.
- Since 2019making software video
- 200+software brands
- ES + ENnative script and voice, no dubbing
- SaaS · IA · WPthe three worlds I cover
Product demos
The shortest path to the moment a product makes sense: the real problem and how it gets solved.
Tutorials and walkthroughs
So users do not drop off after signing up; they work in onboarding, the help center and support.
Explainer videos
Sixty to ninety seconds that turn “what is this?” into “got it”.
Vertical video and clips
9:16 format for social, cut from the same recording.
Software teams I have worked with
- Respond.io
- Jotform
- WPPOOL
- Airia
- MiniMax
- SalesTarget.ai
The independent reviews on my channel are always my opinion; paid production for a brand is labeled separately.
How it is funded, and how I label it.
Video production for software brands (SaaS Master, above) is paid work and is labeled separately from the channel's reviews.
- Affiliate links. Some links on this site, in my videos or in my channel descriptions may be. If you buy through them, the provider may pay me a commission and you pay the same. On the site they carry the “affiliate link” label and the
rel="sponsored"attribute; in videos I say so in the video itself or in the description. - Repos and documentation. Links to GitHub repos and official documentation go direct, with no affiliate code.
- Sponsored content. If a brand pays me, gives me a product or gives me access in exchange for a mention, I say so clearly. A commission does not change my opinion or my verdict.
- Your data. This site uses no cookies or analytics. Privacy (in Spanish).
The full text, with everything that applies, is in Terms, section 6 (in Spanish).
If I get it wrong, I fix it.
- Dates in plain sight. Pages on the site say when they were last updated (today: October 29, 2026), and each repo guide carries its review date.
- A source for every fact. The guides link the source of what they state. If a fact is not in the official documentation, I mark it “no official data” instead of making it up.
- A wrong or outdated fact. Write to me with the link and the source and I will review it. If something in a video is no longer true, tell me in the comments.
- If you are an author or maintainer. If you want to correct your project's description, license or link, or ask me to remove it, write to me and I will handle it promptly.
Ask for a repo or write me.
The most requested videos come from the comments. Tell me what you want to achieve, not just the repo's name.
- How to ask for a repo, and what to tell me so the video answers what you need: Ask me for a repo.
- If you are the author of a repo or have a tool that fits the channel: direct message on TikTok or YouTube. One condition that does not change: every video covers the good and the bad.
- All my links together: iadeguardia.dev/bio.
The tools I explain.
To read and install repos I lean on agents like Claude Code or Codex. On the site I explain these five: what they are, what they are for and what to watch when using them.
- Claude Code
- Codex
- Antigravity
- OpenCode
- GitHub
Why this channel.
There is a huge amount of great open source almost nobody knows about, and plenty of content that just repeats what is trending. Here we do not count stars: we say what the repo does, what license it comes with and what to watch for.
If a repo is archived, I say so. If the README carries a warning, I show it. Those are the channel rules and they do not change. And before installing anything, I give you the guide to checking a repo.
Quick questions.
- Do I need to know how to code to watch the videos?No. To install a repo it helps to know how to open a terminal; each guide has the command to get started.
- Is everything on the channel free and open source?Not always. Some use open-source licenses, others are source-available with restrictions, and almost all of them cost something to run: hardware, hosting or API keys. Each guide states its license and its conditions.
- Do you test every repo yourself?The facts you see come from each repo's README and official documentation, not from lab tests. If I did not try something myself, I do not say I did.
- Can a repo or a brand pay to be featured on the channel?If a brand pays me, gives me a product or gives me access in exchange for a mention, I say so clearly. And every video covers the good and the bad, with the license and the warnings in plain sight.
- Are the videos in English?The channel's videos are in Spanish. The guides, calculators and the rest of this site are available in English too.
- How do I ask for a repo or tell you about a mistake?With a comment on TikTok or YouTube, or by direct message. The details are below.