Esse WhatsApp com IA Opensource é uma grande oportunidade e muitos vão ganhar com isso
DeskcommCRM é um WhatsApp com IA e CRM open source, com licença MIT: você instala na sua VPS, coloca sua marca e vende como SaaS, com mais de 170 pessoas desenvolvendo junto com você.
🤝 Comunidade Deskcomm gratuita (entre e tire dúvidas com quem já instalou): deskcomm.automatiklabs.com.br
👉 VPS HostGator, patrocinadora do canal: hostgator.com.br
🛠️ Instale o Deskcomm na sua VPS (guia passo a passo): deskcomm.com.br
💻 Repositório no GitHub (deixa sua estrela ⭐): melgarafael/DeskcommCRM
🙋 Primeira contribuição, tarefas para iniciantes: github.com/melgarafael/DeskcommCRM/contribute
📚 Curso visual gratuito que se atualiza sozinho: deskcomm.com.br
🧙 Comunidade dos Magos, IA e Vibe Coding (R$ 49,90/mês): lp-comunidade.automatiklabs.com.br
💳 Aula: transforme o Deskcomm num SaaS e cobre assinatura: youtu.be
🆕 Changelog, tudo que a comunidade entregou: deskcomm.com.br
🧑💻 Guia para Devs e contribuidores: deskcomm.com.br
▶ Vídeo anterior: 157 desconhecidos estão desenvolvendo esse CRM: youtu.be
Por muito tempo, quem vendia agente de IA, atendimento ou CRM tinha duas saídas. A primeira era alugar uma ferramenta fechada: caro, sem poder mudar nada, dependendo de alguém gravar curso. A segunda era criar a própria ferramenta sozinho com IA: um loop de criar e corrigir bug que nunca chega à venda. Eu fiz a segunda com o Tomik e gastei mais de R$ 70 mil em tokens antes de começar do zero.
A terceira saída é participar de um projeto open source com licença MIT, como o DeskcommCRM:
1. Aprender: a IA lê o código e explica cada recurso; a comunidade grava e compartilha (foi assim que o n8n cresceu); e o curso visual gratuito se atualiza sozinho a cada recurso novo.
2. Faltou algo: você abre uma issue no GitHub ou implementa e contribui. Hoje mais de 80% do sistema veio de contribuição de quem sentiu falta de alguma coisa.
3. Custo: só a VPS e a IA. Você clona o código, sobe na sua VPS, coloca no seu domínio e a ferramenta é sua.
4. Monetizar: a licença MIT deixa clonar, mudar a marca e vender como SaaS ou como serviço, contribuindo com o projeto ou não.
O que já vem pronto para vender como SaaS (no vídeo, a partir do 13:09):
• Cobrança: você cria o plano (no exemplo, PRO a R$ 997/mês, 7 dias de teste, 20 atendentes, 5 números e US$ 50 de IA) e conecta a Stripe ou o Asaas.
• Tenants: cadastre cada cliente com plano, e-mail do responsável e interface completa ou simplificada (só a parte operacional).
• Marca: cores, logo e ícone do navegador. O cliente vê o sistema como seu.
• Assinatura sozinha: o cliente cria a conta, escolhe o plano e cai na página de pagamento.
• Suporte: com o usuário master você acompanha usuários, conversas, leads e conexões de cada cliente e entra na organização dele para corrigir um problema, sem pedir senha.
Hoje são mais de 5 mil estrelas no GitHub e mais de 170 pessoas desenvolvendo junto. É um time de centenas de pessoas trabalhando com e para você, sem a parte difícil de gerir uma empresa desse tamanho.
⏱️ CAPÍTULOS
00:00 Por que você alugava a estrutura dos outros?
00:57 Tomik: R$ 70 mil em tokens e madrugadas de bugs
02:01 Como nasceu o DeskcommCRM: 5 mil estrelas e 170 pessoas
03:44 Por que alguém libera o próprio trabalho de graça?
04:34 Opção 1: alugar uma ferramenta fechada
06:39 Opção 2: criar sua ferramenta sozinho com IA
07:57 Rigidez × complexidade: onde as duas travam
08:28 Opção 3: participar de um projeto open source
09:39 Comunidade gratuita do Deskcomm
09:52 Faltou um recurso? Abra uma issue ou contribua
10:49 Curso visual gratuito que se atualiza sozinho
11:47 Quanto custa: VPS e o código na sua máquina
12:35 Licença MIT: posso vender como SaaS?
13:19 Como criar planos e cobrar seus clientes
14:34 Stripe ou Asaas: conectando a cobrança
14:49 Sua marca: cores, logo e ícone
15:07 O que o seu cliente vê ao assinar
15:34 Suporte: entrar na conta do cliente sem pedir senha
16:20 Formas de monetizar: SaaS, conteúdo e fork
16:44 Comunidade dos Magos: o curso de 5h40
17:14 Centenas de pessoas trabalhando com e para você
18:06 Agente de IA, follow-up inteligente e casos
Não adianta só assistir: instale o Deskcomm na sua VPS, abra uma issue com o recurso que falta para o seu cliente e entre na comunidade gratuita.
A HostGator patrocina o canal. Ao contratar pelo link acima, você apoia a continuidade do projeto e dos conteúdos gratuitos.
#OpenSource #CRMcomIA #Deskcomm #WhatsAppComIA #SaaS
[en-US] This Open Source AI WhatsApp is a huge opportunity and many will profit from it
DeskcommCRM is an open-source, MIT-licensed WhatsApp-based CRM: you install it on your VPS, add your branding, and sell it as SaaS, with over 170 people developing it alongside you.
🤝 Free Deskcomm Community (join and ask questions to those who have already installed it): deskcomm.automatiklabs.com.br
👉 HostGator VPS, channel sponsor: hostgator.com.br
🛠️ Install Deskcomm on your VPS (step-by-step guide): deskcomm.com.br
💻 GitHub repository (leave your star ⭐): melgarafael/DeskcommCRM
🙋 First contribution, tasks for beginners: github.com/melgarafael/DeskcommCRM/contribute
📚 Free visual course that updates itself: deskcomm.com.br
🧙 Community of Wizards, AI and Vibe Coding (R$ 49.90/month): lp-comunidade.automatiklabs.com.br
💳 Lesson: transform Deskcomm into a SaaS and charge a subscription: youtu.be
🆕 Changelog, everything the community delivered: deskcomm.com.br
🧑💻 Guide for Devs and contributors: deskcomm.com.br
▶ Previous video: 157 strangers are developing this CRM: youtu.be
For a long time, those who sold AI agents, customer service, or CRM had two options. The first was to rent a closed tool: expensive, without being able to change anything, depending on someone recording a course. The second was to create their own tool alone with AI: a loop of creating and fixing bugs that never leads to a sale. I did the second with Tomik and spent over R$ 70,000 on tokens before starting from scratch. The third option is to participate in an open-source project with an MIT license, such as DeskcommCRM:
1. Learning: the AI reads the code and explains each feature; the community records and shares (this is how n8n grew); and the free visual course updates itself with each new feature.
2. Something was missing: you open an issue on GitHub or implement and contribute. Today, more than 80% of the system came from contributions from those who felt something was missing.
3. Cost: only the VPS and the AI. You clone the code, upload it to your VPS, put it on your domain, and the tool is yours.
4. Monetizing: the MIT license allows you to clone, rebrand, and sell as SaaS or as a service, whether you contribute to the project or not.
What comes ready to sell as SaaS (in the video, from 13:09):
• Billing: you create the plan (in the example, PRO at R$ 997/month, 7-day trial, 20 agents, 5 numbers and US$ 50 of AI) and connect Stripe or Asaas.
• Tenants: register each client with a plan, responsible email and complete or simplified interface (only the operational part).
• Branding: colors, logo and browser icon. The client sees the system as their own.
• Self-subscription: the client creates the account, chooses the plan and goes to the payment page.
• Support: with the master user you can track users, conversations, leads and connections of each client and enter their organization to fix a problem, without asking for a password.
Today there are more than 5,000 stars on GitHub and more than 170 people developing together. It's a team of hundreds of people working with and for you, without the difficult part of managing a company of this size. ⏱️ CHAPTERS
00:00 Why were you renting other people's infrastructure?
00:57 Tomik: R$ 70,000 in tokens and late nights dealing with bugs
02:01 How DeskcommCRM was born: 5,000 stars and 170 people
03:44 Why would someone release their own work for free?
04:34 Option 1: Renting a closed tool
06:39 Option 2: Creating your own tool with AI
07:57 Rigidity × complexity: where they both get in the way
08:28 Option 3: Participating in an open source project
09:39 Deskcomm's free community
09:52 Missing a feature? Open an issue or contribute
10:49 Free visual course that updates itself
11:47 How much does it cost: VPS and the code on your machine
12:35 MIT License: Can I sell it as SaaS?
13:19 How to create plans and charge your clients
14:34 Stripe or Asaas: connecting billing
14:49 Your brand: colors, logo and icon
15:07 What your client sees when subscribing
15:34 Support: accessing the client's account without asking for a password
16:20 Ways to monetize: SaaS, content and fork
16:44 Wizards Community: the 5h40 course
17:14 Hundreds of people working with and for you
18:06 AI agent, intelligent follow-up and cases
Just watching isn't enough: install Deskcomm on your VPS, open an issue with the missing feature for your client and join the free community.
HostGator sponsors the channel. By subscribing through the link above, you support the continu...
[es-US] Este WhatsApp con IA de código abierto es una gran oportunidad y muchos se beneficiarán de ello
DeskcommCRM es un CRM de código abierto basado en WhatsApp, con licencia MIT: lo instalas en tu VPS, le añades tu marca y lo vendes como SaaS, con más de 170 personas que lo desarrollan contigo.
🤝 Comunidad gratuita de Deskcomm (únete y haz preguntas a quienes ya lo tienen instalado): deskcomm.automatiklabs.com.br
👉 VPS HostGator, patrocinador del canal: hostgator.com.br
🛠️ Instala Deskcomm en tu VPS (guía paso a paso): deskcomm.com.br
💻 Repositorio de GitHub (deja tu estrella ⭐): melgarafael/DeskcommCRM
🙋 Primera contribución, tareas para principiantes: github.com/melgarafael/DeskcommCRM/contribute
📚 Curso visual gratuito que se actualiza automáticamente: deskcomm.com.br
🧙 Comunidad de magos, IA y programación Vibe (R$ 49,90/mes): lp-comunidade.automatiklabs.com.br
💳 Lección: transforma Deskcomm en un SaaS y cobra una suscripción: youtu.be
🆕 Registro de cambios, todo lo que la comunidad ha aportado: deskcomm.com.br
🧑💻 Guía para desarrolladores y colaboradores: deskcomm.com.br
▶ Video anterior: 157 desconocidos desarrollan este CRM: youtu.be
Durante mucho tiempo, quienes vendían agentes de IA, servicio al cliente o CRM tenían dos opciones. La primera era alquilar una herramienta cerrada: costosa, sin posibilidad de modificar nada y dependiendo de que alguien grabara un curso. La segunda era crear su propia herramienta con IA: un ciclo interminable de creación y corrección de errores que nunca se traducía en una venta. Opté por la segunda opción con Tomik y gasté más de R$ 70.000 en tokens antes de empezar desde cero. La tercera opción es participar en un proyecto de código abierto con licencia MIT, como DeskcommCRM:
1. Aprendizaje: la IA lee el código y explica cada funcionalidad; la comunidad registra y comparte (así creció n8n); y el curso visual gratuito se actualiza con cada nueva funcionalidad.
2. Si faltaba algo: abres una incidencia en GitHub o implementas y contribuyes. Hoy en día, más del 80% del sistema proviene de contribuciones de quienes sentían que faltaba algo.
3. Coste: solo el VPS y la IA. Clonas el código, lo subes a tu VPS, lo alojas en tu dominio y la herramienta es tuya.
4. Monetización: la licencia MIT te permite clonar, cambiar la marca y vender como SaaS o como servicio, independientemente de si contribuyes al proyecto o no.
Lo que viene listo para vender como SaaS (en el video, desde el minuto 13:09):
• Facturación: creas el plan (en el ejemplo, PRO por R$ 997/mes, prueba gratuita de 7 días, 20 agentes, 5 números y US$ 50 de IA) y lo conectas con Stripe o AaaS.
• Clientes: registras a cada cliente con un plan, un correo electrónico responsable y una interfaz completa o simplificada (solo la parte operativa).
• Personalización de marca: colores, logotipo e icono del navegador. El cliente percibe el sistema como propio.
• Autosuscripción: el cliente crea la cuenta, elige el plan y accede a la página de pago.
• Soporte: con el usuario principal puedes realizar un seguimiento de los usuarios, conversaciones, clientes potenciales y conexiones de cada cliente, e ingresar a su organización para solucionar un problema sin necesidad de contraseña.
Actualmente, hay más de 5000 estrellas en GitHub y más de 170 personas desarrollando en conjunto. Es un equipo de cientos de personas trabajando contigo y para ti, sin la parte difícil de administrar una empresa de este tamaño. ⏱️ CAPÍTULOS
00:00 ¿Por qué alquilabas la infraestructura de otros?
00:57 Tomik: R$ 70.000 en tokens y noches en vela solucionando errores
02:01 Cómo nació DeskcommCRM: 5.000 estrellas y 170 personas
03:44 ¿Por qué alguien publicaría su propio trabajo gratis?
04:34 Opción 1: Alquilar una herramienta cerrada
06:39 Opción 2: Crear tu propia herramienta con IA
07:57 Rigidez × complejidad: dónde se interponen ambas
08:28 Opción 3: Participar en un proyecto de código abierto
09:39 La comunidad gratuita de Deskcomm
09:52 ¿Falta alguna función? Abre una incidencia o contribuye
10:49 Curso visual gratuito que se actualiza automáticamente
11:47 ¿Cuánto cuesta?: VPS y el código en tu máquina
12:35 Licencia MIT: ¿Puedo venderlo como SaaS?
13:19 Cómo crear planes y cobrar a tus clientes
14:34 Stripe o SaaS: cómo conectar la facturación
14:49 Tu marca: colores, logotipo e icono
15:07 Qué ve tu cliente al suscribirse
15:34 Soporte: cómo acceder a la cuenta del cliente sin pedir contraseña
16:20 Formas de monetizar: SaaS, contenido y bifurcación
16:44 Comunidad Wizards: el curso de 5h40
17...
89 likes · 21 comments · 4,059 views
Supabase's Default Privileges Expose Every New Table. Here's the Self-Healing Fix.
If you dump a Supabase schema and replay it anywhere — a new project, a template, a customer deployment — your dump quietly re-creates the most dangerous default in the platform: GRANT ALL ON TABLES TO anon. Every table the dump creates after that line is born world-readable to the anon key that ships in your frontend bundle.
Most teams handle this with a code review checklist: "remember to revoke anon on new tables." One open-source CRM with 4,500+ stars handles it better — with a catalog-driven function that finds unprotected tenant tables and locks them automatically, plus a unit test that fails the build if the protection ever stops running last.
This is the anatomy of that trap, and the self-healing pattern that defeats it.
The trap: your own dump re-arms it
Run pg_dump on any Supabase project and look at what comes out near the top:
ALTER DEFAULT PRIVILEGES FOR ROLE "postgres" IN SCHEMA "public"
GRANT ALL ON TABLES TO "anon";
ALTER DEFAULT PRIVILEGES FOR ROLE "postgres" IN SCHEMA "public"
GRANT ALL ON TABLES TO "authenticated";
pg_dump faithfully re-emits the platform's default-privilege entries into pg_default_acl. This is not pg_dump being careless — it's recording the project's actual state. But the effect when you replay that dump is that every CREATE TABLE that follows it — every table in your baseline, every appendix block, every template you ship — inherits the grant before your RLS policies even exist.
The sequence that burns teams:
dump re-emits ALTER DEFAULT PRIVILEGES ... TO anon
→ new table created in the dump
→ table is born granted to anon
→ RLS not yet enabled (or enabled with a permissive policy)
→ PostgREST exposes it with the anon key
RLS being "enabled" later helps — but only if the policies are right. The grant underneath means the table is reachable the moment it exists, and reachable forever if the revoke is forgotten.
Why "remember to revoke" fails
I scan public Supabase repos for exactly this class of issue (results from 100 repos: ~25% with permissive RLS, most of it this pattern). The failure is never ignorance — plenty of teams know anon should be revoked. The failure is remembering, per table, across every migration and every appendix block, forever. One forgotten revoke on one table with customer data is the entire breach.
The naive mitigation — put the ALTER DEFAULT PRIVILEGES revoke at the top of your dump — has its own trap: it changes what future tables inherit, but tables created before your revoke (or by other roles) keep their grants. And the grant to PUBLIC that Postgres gives functions at creation survives revoke from anon — you need both revokes. Miss either source and the surface stays open.
The self-healing pattern
DeskcommCRM — an open-source AI sales CRM (MIT) with a Supabase baseline of 200+ tables — runs this function in the same transaction that provisions new module tables:
create or replace function public.fn_proteger_tabelas_de_organizacao()
returns void language plpgsql set search_path = public as $f$
declare r record;
begin
for r in
select c.relname from pg_class c
join pg_namespace n on n.oid = c.relnamespace
where n.nspname = 'public'
and c.relkind = 'r'
and not c.relrowsecurity -- RLS still off
and exists ( -- and it's a tenant table
select 1 from pg_attribute a
where a.attrelid = c.oid
and a.attname = 'organization_id'
and a.attnum > 0 and not a.attisdropped)
order by c.relname
loop
execute format('alter table public.%I enable row level security', r.relname);
execute format('revoke all on public.%I from anon', r.relname);
execute format('drop policy if exists tenant_isolation_%s_all on public.%I', r.relname, r.relname);
execute format(
'create policy tenant_isolation_%s_all on public.%I for all
using (organization_id in (select * from public.fn_user_org_ids()))
with check (organization_id in (select * from public.fn_user_org_ids()))',
r.relname, r.relname);
end loop;
end $f$;
What it does, line by line:
1. Queries the catalog, not a list. It reads pg_class for every table in public where RLS is still off and the table carries an organization_id column — their multi-tenancy marker. If a module adds a tenant table and forgets RLS, this function finds it anyway. The protection doesn't depend on anyone remembering the table exists.
2. Enables RLS, revokes anon, installs a tenant-isolation policy — all three layers, atomically, per table. The policy keys on fn_user_org_ids() so rows are only visible to members of the owning organization, with with check enforcing it on writes too.
3. Runs as the last step of provisioning, in the same transaction as table creation — the window where the table exists but isn't protected never opens for a concurrent reader.
Their baseline's comments (in Portuguese) state the doctrine outright: new tables are born granted ("tabela nova nasce concedida") and the sweep is what cures them — then they go one step further.
The test that keeps the healer healthy
A sweep that stops running is indistinguishable from no sweep. So the repo includes a unit test with a pointed name: varredura-anon-e-o-ultimo-bloco — "the anon sweep is the last block." It fails the build if the sweep ever stops being the final block of the baseline, because any appendix block added after the sweep would be born granted and never cured.
That's the full maturity ladder in one test:
| Level | Strategy | Fails when |
|---|---|---|
| 1 | Hope + code review | a human forgets once |
| 2 | Explicit revokes per table | one table is added without one |
| 3 | Catalog sweep at provision time | the sweep stops running last |
| 4 | Sweep + test enforcing the sweep's position | (you have to break the test) |
The one-query check for your own project
Whether or not you adopt the pattern, run this today:
select c.relname,
exists(select 1 from pg_class x where x.oid = c.oid and x.relrowsecurity) as rls_on,
has_table_privilege('anon', c.oid, 'SELECT') as anon_can_read
from pg_class c
join pg_namespace n on n.oid = c.relnamespace
where n.nspname = 'public' and c.relkind = 'r'
and has_table_privilege('anon', c.oid, 'SELECT');
Every row returned is a table the anon key in your bundle can read. For multi-tenant tables the row above should not exist at all; if it does, the sweep pattern above is your fix template.
What October 30 changes — and what it doesn't
Supabase's October 30, 2026 change stops the platform from auto-granting anon/authenticated access to new tables in existing projects. That closes the trap at the platform level for platform defaults — but it does not touch two things:
1. Your own dumps and templates. If your baseline or install template re-emits the old ALTER DEFAULT PRIVILEGES ... GRANT ALL TO anon (as pg_dump does), your deployments re-arm the trap regardless of what the platform does. The DeskcommCRM approach — explicit management plus an automated, tested sweep — is immune precisely because it never trusted the platform default in either direction.
2. Tables that already exist. The change affects new tables; the grants already sitting in your catalog stay until you revoke them.
The general lesson survives any platform change: don't rely on defaults, old or new. Make your protections explicit, make them catalog-driven, and make a test prove they run.
---
References: the DeskcommCRM baseline (MIT, Rafael Melgaço) for the sweep pattern and its enforcement test; my 100-repo scan data for the prevalence numbers; the Supabase docs on role privileges for the default-grant behavior.
Mentions
客户都在 WhatsApp 里聊，聊完还得手动往 CRM 抄？ DeskcommCRM 是自托管 AI 销售系统：AI agent 直接在 WhatsApp 里接单、筛客户、跟进，整套跑在你自己的服务器上。 适合靠聊天卖货的小团队。 你会先让 agent 接哪类客户咨询，问价还是售后？ #销售 #AI @grok melgarafael/DeskcommCRM
Esse WhatsApp com IA Opensource é uma grande oportunidade e muitos vão ganhar com isso DeskcommCRM é um WhatsApp com IA e CRM open source, com licença MIT: você instala na sua VPS, coloca sua marca e vende como SaaS, com mais de 170 pessoas desenvolvendo junto com você. 🤝 Comunidade Deskcomm gratuita (entre e tire dúvidas com quem já instalou): deskcomm.automatiklabs.com.br 👉 VPS HostGator, patrocinadora do canal: hostgator.com.br 🛠️ Instale o Deskcomm na sua VPS (guia passo a passo): deskcomm.com.br 💻 Repositório no GitHub (deixa sua estrela ⭐): melgarafael/DeskcommCRM 🙋 Primeira contribuição, tarefas para iniciantes: github.com/melgarafael/DeskcommCRM/contribute 📚 Curso visual gratuito que se atualiza sozinho: deskcomm.com.br 🧙 Comunidade dos Magos, IA e Vibe Coding (R$ 49,90/mês): lp-comunidade.automatiklabs.com.br 💳 Aula: transforme o Deskcomm num SaaS e cobre assinatura: youtu.be 🆕 Changelog, tudo que a comunidade entregou: deskcomm.com.br 🧑💻 Guia para Devs e contribuidores: deskcomm.com.br ▶ Vídeo anterior: 157 desconhecidos estão desenvolvendo esse CRM: youtu.be Por muito tempo, quem vendia agente de IA, atendimento ou CRM tinha duas saídas. A primeira era alugar uma ferramenta fechada: caro, sem poder mudar nada, dependendo de alguém gravar curso. A segunda era criar a própria ferramenta sozinho com IA: um loop de criar e corrigir bug que nunca chega à venda. Eu fiz a segunda com o Tomik e gastei mais de R$ 70 mil em tokens antes de começar do zero. A terceira saída é participar de um projeto open source com licença MIT, como o DeskcommCRM: 1. Aprender: a IA lê o código e explica cada recurso; a comunidade grava e compartilha (foi assim que o n8n cresceu); e o curso visual gratuito se atualiza sozinho a cada recurso novo. 2. Faltou algo: você abre uma issue no GitHub ou implementa e contribui. Hoje mais de 80% do sistema veio de contribuição de quem sentiu falta de alguma coisa. 3. Custo: só a VPS e a IA. Você clona o código, sobe na sua VPS, coloca no seu domínio e a ferramenta é sua. 4. Monetizar: a licença MIT deixa clonar, mudar a marca e vender como SaaS ou como serviço, contribuindo com o projeto ou não. O que já vem pronto para vender como SaaS (no vídeo, a partir do 13:09): • Cobrança: você cria o plano (no exemplo, PRO a R$ 997/mês, 7 dias de teste, 20 atendentes, 5 números e US$ 50 de IA) e conecta a Stripe ou o Asaas. • Tenants: cadastre cada cliente com plano, e-mail do responsável e interface completa ou simplificada (só a parte operacional). • Marca: cores, logo e ícone do navegador. O cliente vê o sistema como seu. • Assinatura sozinha: o cliente cria a conta, escolhe o plano e cai na página de pagamento. • Suporte: com o usuário master você acompanha usuários, conversas, leads e conexões de cada cliente e entra na organização dele para corrigir um problema, sem pedir senha. Hoje são mais de 5 mil estrelas no GitHub e mais de 170 pessoas desenvolvendo junto. É um time de centenas de pessoas trabalhando com e para você, sem a parte difícil de gerir uma empresa desse tamanho. ⏱️ CAPÍTULOS 00:00 Por que você alugava a estrutura dos outros? 00:57 Tomik: R$ 70 mil em tokens e madrugadas de bugs 02:01 Como nasceu o DeskcommCRM: 5 mil estrelas e 170 pessoas 03:44 Por que alguém libera o próprio trabalho de graça? 04:34 Opção 1: alugar uma ferramenta fechada 06:39 Opção 2: criar sua ferramenta sozinho com IA 07:57 Rigidez × complexidade: onde as duas travam 08:28 Opção 3: participar de um projeto open source 09:39 Comunidade gratuita do Deskcomm 09:52 Faltou um recurso? Abra uma issue ou contribua 10:49 Curso visual gratuito que se atualiza sozinho 11:47 Quanto custa: VPS e o código na sua máquina 12:35 Licença MIT: posso vender como SaaS? 13:19 Como criar planos e cobrar seus clientes 14:34 Stripe ou Asaas: conectando a cobrança 14:49 Sua marca: cores, logo e ícone 15:07 O que o seu cliente vê ao assinar 15:34 Suporte: entrar na conta do cliente sem pedir senha 16:20 Formas de monetizar: SaaS, conteúdo e fork 16:44 Comunidade dos Magos: o curso de 5h40 17:14 Centenas de pessoas trabalhando com e para você 18:06 Agente de IA, follow-up inteligente e casos Não adianta só assistir: instale o Deskcomm na sua VPS, abra uma issue com o recurso que falta para o seu cliente e entre na comunidade gratuita. A HostGator patrocina o canal. Ao contratar pelo link acima, você apoia a continuidade do projeto e dos conteúdos gratuitos. #OpenSource #CRMcomIA #Deskcomm #WhatsAppComIA #SaaS [en-US] This Open Source AI WhatsApp is a huge opportunity and many will profit from it DeskcommCRM is an open-source, MIT-licensed WhatsApp-based CRM: you install it on your VPS, add your branding, and sell it as SaaS, with over 170 people developing it alongside you. 🤝 Free Deskcomm Community (join and ask questions to those who have already installed it): deskcomm.automatiklabs.com.br 👉 HostGator VPS, channel sponsor: hostgator.com.br 🛠️ Install Deskcomm on your VPS (step-by-step guide): deskcomm.com.br 💻 GitHub repository (leave your star ⭐): melgarafael/DeskcommCRM 🙋 First contribution, tasks for beginners: github.com/melgarafael/DeskcommCRM/contribute 📚 Free visual course that updates itself: deskcomm.com.br 🧙 Community of Wizards, AI and Vibe Coding (R$ 49.90/month): lp-comunidade.automatiklabs.com.br 💳 Lesson: transform Deskcomm into a SaaS and charge a subscription: youtu.be 🆕 Changelog, everything the community delivered: deskcomm.com.br 🧑💻 Guide for Devs and contributors: deskcomm.com.br ▶ Previous video: 157 strangers are developing this CRM: youtu.be For a long time, those who sold AI agents, customer service, or CRM had two options. The first was to rent a closed tool: expensive, without being able to change anything, depending on someone recording a course. The second was to create their own tool alone with AI: a loop of creating and fixing bugs that never leads to a sale. I did the second with Tomik and spent over R$ 70,000 on tokens before starting from scratch. The third option is to participate in an open-source project with an MIT license, such as DeskcommCRM: 1. Learning: the AI reads the code and explains each feature; the community records and shares (this is how n8n grew); and the free visual course updates itself with each new feature. 2. Something was missing: you open an issue on GitHub or implement and contribute. Today, more than 80% of the system came from contributions from those who felt something was missing. 3. Cost: only the VPS and the AI. You clone the code, upload it to your VPS, put it on your domain, and the tool is yours. 4. Monetizing: the MIT license allows you to clone, rebrand, and sell as SaaS or as a service, whether you contribute to the project or not. What comes ready to sell as SaaS (in the video, from 13:09): • Billing: you create the plan (in the example, PRO at R$ 997/month, 7-day trial, 20 agents, 5 numbers and US$ 50 of AI) and connect Stripe or Asaas. • Tenants: register each client with a plan, responsible email and complete or simplified interface (only the operational part). • Branding: colors, logo and browser icon. The client sees the system as their own. • Self-subscription: the client creates the account, chooses the plan and goes to the payment page. • Support: with the master user you can track users, conversations, leads and connections of each client and enter their organization to fix a problem, without asking for a password. Today there are more than 5,000 stars on GitHub and more than 170 people developing together. It's a team of hundreds of people working with and for you, without the difficult part of managing a company of this size. ⏱️ CHAPTERS 00:00 Why were you renting other people's infrastructure? 00:57 Tomik: R$ 70,000 in tokens and late nights dealing with bugs 02:01 How DeskcommCRM was born: 5,000 stars and 170 people 03:44 Why would someone release their own work for free? 04:34 Option 1: Renting a closed tool 06:39 Option 2: Creating your own tool with AI 07:57 Rigidity × complexity: where they both get in the way 08:28 Option 3: Participating in an open source project 09:39 Deskcomm's free community 09:52 Missing a feature? Open an issue or contribute 10:49 Free visual course that updates itself 11:47 How much does it cost: VPS and the code on your machine 12:35 MIT License: Can I sell it as SaaS? 13:19 How to create plans and charge your clients 14:34 Stripe or Asaas: connecting billing 14:49 Your brand: colors, logo and icon 15:07 What your client sees when subscribing 15:34 Support: accessing the client's account without asking for a password 16:20 Ways to monetize: SaaS, content and fork 16:44 Wizards Community: the 5h40 course 17:14 Hundreds of people working with and for you 18:06 AI agent, intelligent follow-up and cases Just watching isn't enough: install Deskcomm on your VPS, open an issue with the missing feature for your client and join the free community. HostGator sponsors the channel. By subscribing through the link above, you support the continu... [es-US] Este WhatsApp con IA de código abierto es una gran oportunidad y muchos se beneficiarán de ello DeskcommCRM es un CRM de código abierto basado en WhatsApp, con licencia MIT: lo instalas en tu VPS, le añades tu marca y lo vendes como SaaS, con más de 170 personas que lo desarrollan contigo. 🤝 Comunidad gratuita de Deskcomm (únete y haz preguntas a quienes ya lo tienen instalado): deskcomm.automatiklabs.com.br 👉 VPS HostGator, patrocinador del canal: hostgator.com.br 🛠️ Instala Deskcomm en tu VPS (guía paso a paso): deskcomm.com.br 💻 Repositorio de GitHub (deja tu estrella ⭐): melgarafael/DeskcommCRM 🙋 Primera contribución, tareas para principiantes: github.com/melgarafael/DeskcommCRM/contribute 📚 Curso visual gratuito que se actualiza automáticamente: deskcomm.com.br 🧙 Comunidad de magos, IA y programación Vibe (R$ 49,90/mes): lp-comunidade.automatiklabs.com.br 💳 Lección: transforma Deskcomm en un SaaS y cobra una suscripción: youtu.be 🆕 Registro de cambios, todo lo que la comunidad ha aportado: deskcomm.com.br 🧑💻 Guía para desarrolladores y colaboradores: deskcomm.com.br ▶ Video anterior: 157 desconocidos desarrollan este CRM: youtu.be Durante mucho tiempo, quienes vendían agentes de IA, servicio al cliente o CRM tenían dos opciones. La primera era alquilar una herramienta cerrada: costosa, sin posibilidad de modificar nada y dependiendo de que alguien grabara un curso. La segunda era crear su propia herramienta con IA: un ciclo interminable de creación y corrección de errores que nunca se traducía en una venta. Opté por la segunda opción con Tomik y gasté más de R$ 70.000 en tokens antes de empezar desde cero. La tercera opción es participar en un proyecto de código abierto con licencia MIT, como DeskcommCRM: 1. Aprendizaje: la IA lee el código y explica cada funcionalidad; la comunidad registra y comparte (así creció n8n); y el curso visual gratuito se actualiza con cada nueva funcionalidad. 2. Si faltaba algo: abres una incidencia en GitHub o implementas y contribuyes. Hoy en día, más del 80% del sistema proviene de contribuciones de quienes sentían que faltaba algo. 3. Coste: solo el VPS y la IA. Clonas el código, lo subes a tu VPS, lo alojas en tu dominio y la herramienta es tuya. 4. Monetización: la licencia MIT te permite clonar, cambiar la marca y vender como SaaS o como servicio, independientemente de si contribuyes al proyecto o no. Lo que viene listo para vender como SaaS (en el video, desde el minuto 13:09): • Facturación: creas el plan (en el ejemplo, PRO por R$ 997/mes, prueba gratuita de 7 días, 20 agentes, 5 números y US$ 50 de IA) y lo conectas con Stripe o AaaS. • Clientes: registras a cada cliente con un plan, un correo electrónico responsable y una interfaz completa o simplificada (solo la parte operativa). • Personalización de marca: colores, logotipo e icono del navegador. El cliente percibe el sistema como propio. • Autosuscripción: el cliente crea la cuenta, elige el plan y accede a la página de pago. • Soporte: con el usuario principal puedes realizar un seguimiento de los usuarios, conversaciones, clientes potenciales y conexiones de cada cliente, e ingresar a su organización para solucionar un problema sin necesidad de contraseña. Actualmente, hay más de 5000 estrellas en GitHub y más de 170 personas desarrollando en conjunto. Es un equipo de cientos de personas trabajando contigo y para ti, sin la parte difícil de administrar una empresa de este tamaño. ⏱️ CAPÍTULOS 00:00 ¿Por qué alquilabas la infraestructura de otros? 00:57 Tomik: R$ 70.000 en tokens y noches en vela solucionando errores 02:01 Cómo nació DeskcommCRM: 5.000 estrellas y 170 personas 03:44 ¿Por qué alguien publicaría su propio trabajo gratis? 04:34 Opción 1: Alquilar una herramienta cerrada 06:39 Opción 2: Crear tu propia herramienta con IA 07:57 Rigidez × complejidad: dónde se interponen ambas 08:28 Opción 3: Participar en un proyecto de código abierto 09:39 La comunidad gratuita de Deskcomm 09:52 ¿Falta alguna función? Abre una incidencia o contribuye 10:49 Curso visual gratuito que se actualiza automáticamente 11:47 ¿Cuánto cuesta?: VPS y el código en tu máquina 12:35 Licencia MIT: ¿Puedo venderlo como SaaS? 13:19 Cómo crear planes y cobrar a tus clientes 14:34 Stripe o SaaS: cómo conectar la facturación 14:49 Tu marca: colores, logotipo e icono 15:07 Qué ve tu cliente al suscribirse 15:34 Soporte: cómo acceder a la cuenta del cliente sin pedir contraseña 16:20 Formas de monetizar: SaaS, contenido y bifurcación 16:44 Comunidad Wizards: el curso de 5h40 17...
30 projetos GRÁTIS do GitHub para trabalhar melhor com IA Descubra 30 projetos gratuitos do GitHub para usar IA, criar conteúdo e organizar seu trabalho. Veja ferramentas de vídeo, produtividade, segurança, marketing e servidores, com os links organizados por assunto abaixo. Conheça o Bora Criar com IA: boracriarcomia.com.br CAPÍTULOS 00:00 Apresentação e inteligência artificial 00:35 Segurança 00:47 Vídeo e conteúdo 01:10 Negócios e marketing 01:30 Produtividade 01:46 Servidores e infraestrutura 02:23 Projetos para explorar 02:38 Antes de instalar INTELIGÊNCIA ARTIFICIAL 1. Dify — langgenius/dify 2. Taskosaur — Taskosaur/Taskosaur 3. OpenWork — different-ai/openwork 4. Agent Browser — vercel-labs/agent-browser 5. Emdash — generalaction/emdash SEGURANÇA 6. PasteGuard — sgasser/pasteguard 7. Claude Code Safety Net — kenryu42/claude-code-safety-net VÍDEO E CONTEÚDO 8. OpenReel — Augani/openreel-video 9. BridgeClip — bridge-mind/bridgeclip 10. Recordly — webadderall/Recordly 11. Textream — f/textream 12. FFmpeg Skill — kajisho5/ffmpeg-skill 13. Presenton — presenton/presenton NEGÓCIOS E MARKETING 14. Deskcomm CRM — melgarafael/DeskcommCRM 15. Open SEO — every-app/open-seo 16. Cogsend — deepakness/cogsend PRODUTIVIDADE 17. Handy — cjpais/Handy 18. Kept — ericerkz/kept 19. Excalidraw MCP — excalidraw/excalidraw-mcp 20. ezBookkeeping — mayswind/ezbookkeeping SERVIDORES E INFRAESTRUTURA 21. Dockge — louislam/dockge 22. OpenObserve — openobserve/openobserve 23. LogDeck — AmoabaKelvin/logdeck 24. WebSSH — bifrost0x/webssh 25. Breakscale — xevrion/breakscale 26. SQLit — Maxteabag/sqlit 27. Mailflare — hieunc229/mailflare 28. Open Archiver — LogicLabs-OU/OpenArchiver PROJETOS PARA EXPLORAR 29. Vibecraft — Nearcyan/vibecraft 30. God's Eye View — bilawalsidhu/gods-eye-view Confira licença, requisitos, custos de hospedagem e manutenção de cada projeto antes de instalar. “Gratuito” pode depender de serviços externos. Referência de pauta: Hallen Tech — youtube.com Qual ferramenta você vai testar primeiro? Deixe nos comentários e inscreva-se para conhecer mais recursos de IA. #InteligenciaArtificial #GitHub #OpenSource
Github上最全赚钱投资指南的作者 罗列了X上最值得关注的 AI 头部博主清单 太高质了 codeman008/awesome-ai-x-influencers 还没看过最全赚钱投资指南的 传送门在这里 codeman008/Financial_freedom t.co
Supabase's Default Privileges Expose Every New Table. Here's the Self-Healing Fix. If you dump a Supabase schema and replay it anywhere — a new project, a template, a customer deployment — your dump quietly re-creates the most dangerous default in the platform: GRANT ALL ON TABLES TO anon. Every table the dump creates after that line is born world-readable to the anon key that ships in your frontend bundle. Most teams handle this with a code review checklist: "remember to revoke anon on new tables." One open-source CRM with 4,500+ stars handles it better — with a catalog-driven function that finds unprotected tenant tables and locks them automatically, plus a unit test that fails the build if the protection ever stops running last. This is the anatomy of that trap, and the self-healing pattern that defeats it. The trap: your own dump re-arms it Run pg_dump on any Supabase project and look at what comes out near the top: ALTER DEFAULT PRIVILEGES FOR ROLE "postgres" IN SCHEMA "public" GRANT ALL ON TABLES TO "anon"; ALTER DEFAULT PRIVILEGES FOR ROLE "postgres" IN SCHEMA "public" GRANT ALL ON TABLES TO "authenticated"; pg_dump faithfully re-emits the platform's default-privilege entries into pg_default_acl. This is not pg_dump being careless — it's recording the project's actual state. But the effect when you replay that dump is that every CREATE TABLE that follows it — every table in your baseline, every appendix block, every template you ship — inherits the grant before your RLS policies even exist. The sequence that burns teams: dump re-emits ALTER DEFAULT PRIVILEGES ... TO anon → new table created in the dump → table is born granted to anon → RLS not yet enabled (or enabled with a permissive policy) → PostgREST exposes it with the anon key RLS being "enabled" later helps — but only if the policies are right. The grant underneath means the table is reachable the moment it exists, and reachable forever if the revoke is forgotten. Why "remember to revoke" fails I scan public Supabase repos for exactly this class of issue (results from 100 repos: ~25% with permissive RLS, most of it this pattern). The failure is never ignorance — plenty of teams know anon should be revoked. The failure is remembering, per table, across every migration and every appendix block, forever. One forgotten revoke on one table with customer data is the entire breach. The naive mitigation — put the ALTER DEFAULT PRIVILEGES revoke at the top of your dump — has its own trap: it changes what future tables inherit, but tables created before your revoke (or by other roles) keep their grants. And the grant to PUBLIC that Postgres gives functions at creation survives revoke from anon — you need both revokes. Miss either source and the surface stays open. The self-healing pattern DeskcommCRM — an open-source AI sales CRM (MIT) with a Supabase baseline of 200+ tables — runs this function in the same transaction that provisions new module tables: create or replace function public.fn_proteger_tabelas_de_organizacao() returns void language plpgsql set search_path = public as $f$ declare r record; begin for r in select c.relname from pg_class c join pg_namespace n on n.oid = c.relnamespace where n.nspname = 'public' and c.relkind = 'r' and not c.relrowsecurity -- RLS still off and exists ( -- and it's a tenant table select 1 from pg_attribute a where a.attrelid = c.oid and a.attname = 'organization_id' and a.attnum > 0 and not a.attisdropped) order by c.relname loop execute format('alter table public.%I enable row level security', r.relname); execute format('revoke all on public.%I from anon', r.relname); execute format('drop policy if exists tenant_isolation_%s_all on public.%I', r.relname, r.relname); execute format( 'create policy tenant_isolation_%s_all on public.%I for all using (organization_id in (select * from public.fn_user_org_ids())) with check (organization_id in (select * from public.fn_user_org_ids()))', r.relname, r.relname); end loop; end $f$; What it does, line by line: 1. Queries the catalog, not a list. It reads pg_class for every table in public where RLS is still off and the table carries an organization_id column — their multi-tenancy marker. If a module adds a tenant table and forgets RLS, this function finds it anyway. The protection doesn't depend on anyone remembering the table exists. 2. Enables RLS, revokes anon, installs a tenant-isolation policy — all three layers, atomically, per table. The policy keys on fn_user_org_ids() so rows are only visible to members of the owning organization, with with check enforcing it on writes too. 3. Runs as the last step of provisioning, in the same transaction as table creation — the window where the table exists but isn't protected never opens for a concurrent reader. Their baseline's comments (in Portuguese) state the doctrine outright: new tables are born granted ("tabela nova nasce concedida") and the sweep is what cures them — then they go one step further. The test that keeps the healer healthy A sweep that stops running is indistinguishable from no sweep. So the repo includes a unit test with a pointed name: varredura-anon-e-o-ultimo-bloco — "the anon sweep is the last block." It fails the build if the sweep ever stops being the final block of the baseline, because any appendix block added after the sweep would be born granted and never cured. That's the full maturity ladder in one test: | Level | Strategy | Fails when | |---|---|---| | 1 | Hope + code review | a human forgets once | | 2 | Explicit revokes per table | one table is added without one | | 3 | Catalog sweep at provision time | the sweep stops running last | | 4 | Sweep + test enforcing the sweep's position | (you have to break the test) | The one-query check for your own project Whether or not you adopt the pattern, run this today: select c.relname, exists(select 1 from pg_class x where x.oid = c.oid and x.relrowsecurity) as rls_on, has_table_privilege('anon', c.oid, 'SELECT') as anon_can_read from pg_class c join pg_namespace n on n.oid = c.relnamespace where n.nspname = 'public' and c.relkind = 'r' and has_table_privilege('anon', c.oid, 'SELECT'); Every row returned is a table the anon key in your bundle can read. For multi-tenant tables the row above should not exist at all; if it does, the sweep pattern above is your fix template. What October 30 changes — and what it doesn't Supabase's October 30, 2026 change stops the platform from auto-granting anon/authenticated access to new tables in existing projects. That closes the trap at the platform level for platform defaults — but it does not touch two things: 1. Your own dumps and templates. If your baseline or install template re-emits the old ALTER DEFAULT PRIVILEGES ... GRANT ALL TO anon (as pg_dump does), your deployments re-arm the trap regardless of what the platform does. The DeskcommCRM approach — explicit management plus an automated, tested sweep — is immune precisely because it never trusted the platform default in either direction. 2. Tables that already exist. The change affects new tables; the grants already sitting in your catalog stay until you revoke them. The general lesson survives any platform change: don't rely on defaults, old or new. Make your protections explicit, make them catalog-driven, and make a test prove they run. --- References: the DeskcommCRM baseline (MIT, Rafael Melgaço) for the sweep pattern and its enforcement test; my 100-repo scan data for the prevalence numbers; the Supabase docs on role privileges for the default-grant behavior.