Signal House

You can describe an entire app to Claude and ship it in 4 hours. Then you add SMS and suddenly it's 2015 again. CPaaS wasn't built for how we build now. We fixed that.

The CPaaS market hasn't changed in 15 years. Same players. Same slow APIs. Same pricing. We're AI-first from the ground up, smarter routing, faster approvals, one-click integrations. The old guard is sleeping.

You're overpaying for SMS. Legacy CPaaS providers (like Twilio) built their pricing before AI existed. We rebuilt everything from scratch. The savings show up on day one.

Every year Twilio makes A2P compliance more "specific." Every year the gap between "I want to send SMS" and "you can send SMS" gets wider. We built a bridge.

Twilio was built for engineers who read docs. Vibe coders don't read docs. That's literally the whole point. We built the SMS/voice API you prompt, not parse.

@ignacio_jsx @SendGridSupport @twilio Yikes. Give us a look when you get things sorted: signalhouse.io

@SendGridSupport @twilio I am DONE. 15+ days. 3 tickets. Countless copy-paste responses. You keep asking me to rotate API keys TO LOG IN — but my account IS BLOCKED AND I CANNOT LOG IN. This is the most incompetent support I have ever experienced. My business is bleeding money.

You vibe-coded a full app last weekend. Then you tried to add SMS and spent 3 days reading Twilio docs written in 2019. We've changed that.

25% of GenAI enterprises deploying AI agents by year-end (doubling to 50% by 2027). These agents need comms infrastructure and they need it without a telecom PhD.

@karpathy The vibe coding workflow is perfect until you hit "add SMS." We built the API that lets you stay in that flow, describe what you need, it ships.

There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.

You can vibe-code an entire SaaS in a weekend. Auth. Payments. Dashboards. Automations. Then you try to add SMS. Suddenly it's 10DLC registrations, A2P compliance, carrier filtering, and a Twilio console that looks like a 2008 enterprise portal. The vibes are gone. We fixed that.

We spoke at a developer meetup last month, around 200 developers. Asked the room: "How many of you successfully registered an A2P 10DLC brand on the first try?" Three hands went up. Two of them worked at Twilio.

A founder told me her users weren't receiving texts. She checked her Twilio dashboard. Everything said "delivered." Turns out carriers were filtering her messages. Her 10DLC campaign use case said "marketing." Her texts said "your order shipped." The fix was re-registering the campaign. The wait time was six weeks.

@SlamingDev SMS/voice belongs on this list too. most vibe coders hit Twilio, spend 2 weeks on 10DLC registration, and just give up on the feature. Built Signal House so adding comms is a single prompt.

Vibe coding will probably ends up with a lot of apps like this unfortunately, security aside, this can cost $$$ in API usage and turn into nightmare for makers/entreprises. Not blaming builders (that’s cool anyone can finally code their ideas) but more the AI that should not only deliver the answer straight away, but also prevent the risk. Warn, educate, teach. Gonna be disasters for entreprise-grade software otherwise

@karpathy Agentic engineering needs agentic infrastructure. Everything ships via prompt now except communications — SMS and voice APIs still feel like 2015. Working on that.

A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective - I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite "agentic engineering": - "agentic" because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight. - "engineering" to emphasize that there is an art & science and expertise to it. It's something you can learn and become better at, with its own depth of a different kind. In 2026, we're likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.

@rileybrown Solid guide. One thing that trips up every Cursor project eventually: adding SMS or voice. No good vibe-coding path exists for CPaaS yet — that's the gap we're filling

Everyone is talking about Vibe Coding (Using AI to Create Apps Only using AI) This is the most Comprehensive Guide for Vibe Coding with Cursor (By Far) 250 Minutes, All the vibe code basics of cursor, plus 4 Projects in one video! This is how I, as someone who has never written a line of code, approach building apps (every day). Part 1A Intro to Cursor, Composer, and some basics --------------------- 00:00 Intro 03:41 Downloading Cursor 06:09 What the hell is Composer? 10:47 A Note on Context and Keeping Composer Threads Small 11:38 Simple Desings with Cursor Composer From Blank Project 14:04 Editing a Simple Animation With Cursor Composer 16:35 Setting Up The Voice to Talk to Cursor Composer Whispr Flow 17:54 Lets an Early 2000's Landing Page Part 1B AI Image Generator --------------------- 23:59 Using the GitHub Template to Create a NextJS App 26:43 Template is Open, Let's Edit it 28:55 Drawing Out My Idea With Whimsical 30:11 First Prompt Using Place Holders For Image Generation 32:10 Accept All Vs Save All and Restoring in Composer (Saving your work) 33:54 Adding AI Feature (Brief Teaser, Deep Dive Later) 35:15 What is an API 37:22 Perplexity the best place to learn about API's 40:21 Api keys and running prompt for first AI Feature 42:48 Debugging, Woohoo! Learn to love this :) 43:20 Inspect - Console, In Browser Debugging Hack 48:02 AI Image Generation Works! Lets add more Part 2: Landing Page ---------------------- 51:03 Pause and Reflect, What have we done so far? 53:41 Plan for rest of video 54:34 Ok Let's Talk about (1) Designs 56:19 GitHub is like --sref for those who do image gen 58:20 Starting Cursor project from a GitHub Repo we found on Perplexity 01:00:48 Yolo Mode... Wtf is that? 01:02:38 Inspecting GitHub Repo's Examples, to use in our landing page 01:02:58 The Project We're making - A landing page 01:03:56 Landing Page from Screenshot 01:06:17 Making Changes to Landing Page 01:11:42 Making a more epic section 01:13:42 The Essence of Vibe Coding 01:15:17 Creating Cool Testimonials Section From Screenshot 01:18:18 Deploy to Vercel! But First New Repo on GitHub 01:20:45 Ok it's on GitHub... Now lets do vercel 01:21:17 Untechnical Explanation of what Vercel is Lol 01:24:18 Connecting Custom Domain (Bought on Name Cheap) To Vercel Deployment Part 3: App With Database and Authentication ---------------------- 01:27:59 Recap and Prep For The Bigger Project! 01:35:13 Getting Started from Template (Again) 01:38:52 Setting Up Database and Authentication (Firebase) 01:44:01 Back To Cursor, Let's Set up The Auth in the app 01:48:35 Switching to mermaid because compatibility issues 01:51:13 Using AI (Claude) to Generate Mermaid Diagrams 01:52:19 Adding Docs to Cursor to use AI Features over and over again 01:54:38 Let's Troubleshoot 01:56:10 Adding View Button and EDIT WITH AI 02:01:45 AI Diagram Edit Feature is DOPE 02:03:17 Using Search Feature on Cursor to find text in Codebase 02:05:55 Lets add ability to save these to Database 02:09:33 What does saved to Google Firebase even mean? 02:13:00 We can Export as PDF! 02:15:48 GitHub and Vercel Again! 02:17:27 Vercel with CLI From Cursor 02:20:52 Setting Vercel Domain as an Authorized Domain 02:27:34 How To Learn More

CPaaS docs were written in 2015 for enterprise devs with 6-week onboarding cycles. Ai engineers ship apps in 2 hours. The whole category needs a reset. That's why we built Signal House.

Building your platform on Claude? Your comm layer should be just as easy. Introducing our "One-Click" integration layer. Just copy and send to your LLM. loom.com/share/4f82b84f…

The vibe coding workflow in 2026: Day 1: Build entire SaaS with Claude Code. Day 2: Add payments. Done in 2 hours. Day 3: Add auth. Done in 90 minutes. Day 4: Try to add SMS. Step 1: Sign up for Twilio. Step 2: Register a brand. Wait. Step 3: Register a campaign. Wait more. Step 4: Apply for 10DLC. Wait 3 weeks. Day 25: First text delivered. The stack caught up to the developer everywhere except one place.

@rileybrown @karpathy The lesson from Amazon isn't "don't vibe code." It's "vibe code the app, not the infrastructure." Comms, among other layers, is infrastructure.

Vibe Coding: The act of using only your voice in Cursor Composer to build apps, forgetting the code even exists Complete Video Tutorial Some people are skeptical about this new method of programming so why don't we build a ChatGPT clone with real time voice ( @karpathy 's voice) without typing, using Whispr Flow. For me "vibe coding" is my only option. Because i've never written a line of code. Time Stamps: 00:00 Intro to Vibe Coding (pretty corny) 03:02 Opening Cursor 04:07 Starting Your First Project from Template Link (Pinned to bio of @senior_swc ) 05:12 Building a ChatGPT Clone, Getting Started 06:38 Prompting, API's and Documentation Explanation 08:49 Using Perplexity (Input output custom spaces for coding) 12:07 Vibe Code Prompt 1 13:58 Result of Vibe Coding Prompt 1 15:22 Seeing Prompt 2 15:43 Managing Cursor Composer Context Length 16:25 Designing 17:21 Debugging with Inspect on Web View 18:20 Fixing Formatting 19:04 More Vibing, Lol 20:51 Saving and Uploading Projects to GitHub 21:59 Enhancing the User Experience 22:33 Honoring @karpathy 26:26 Implementing Real Time Karpathy Voice 28:30 Getting Karpathys Voice (Don't Do this It's Illegal) @elevenlabs don't ban me i love you

ElevenLabs just raised $500M at an $11B valuation. $330M ARR. The largest voice AI round in history. Voice agents are everywhere now. Every one of them eventually needs to call a real phone number. Outbound dialing. IVR. Carrier routing. Compliance. The voice agent ecosystem is growing 10x a year. The voice infrastructure layer is still 2015 technology. The bottleneck has moved. Nobody's noticed yet.

@naval The bottleneck is shifting fast. Vibe coders ship full-stack apps in hours, then spend 3 days wiring up SMS. The comms layer hasn't caught up. We're fixing that.

Vibe Coding Is the New Product Management “There’s been a shift—a marked pronouncement in the last year and especially in the last few months—most pronounced by Claude Code, which is a specific model that has a coding engine in it, which is so good that I think now you have vibe coders, which are people who didn’t really code much or hadn’t coded in a long time, who are using essentially English as a programming language—as an input into this code bot—which can do end-to-end coding. Instead of just helping you debug things in the middle, you can describe an application that you want. You can have it lay out a plan, you can have it interview you for the plan. You can give it feedback along the way, and then it’ll chunk it up and will build all the scaffolding. It’ll download all the libraries and all the connectors and all the hooks, and it’ll start building your app and building test harnesses and testing it. And you can keep giving it feedback and debugging it by voice, saying, “This doesn’t work. That works. Change this. Change that,” and have it build you an entire working application without your having written a single line of code. For a large group of people who either don’t code anymore or never did, this is mind-blowing. This is taking them from idea space, and opinion space, and from taste directly into product. So that’s what I mean—product management has taken over coding. Vibe coding is the new product management. Instead of trying to manage a product or a bunch of engineers by telling them what to do, you’re now telling a computer what to do. And the computer is tireless. The computer is egoless, and it’ll just keep working. It’ll take feedback without getting offended. You can spin up multiple instances. It’ll work 24/7 and you can have it produce working output. What does that mean? Just like now anybody can make a video or anyone can make a podcast, anyone can now make an application. So we should expect to see a tsunami of applications. Not that we don’t have one already in the App Store, but it doesn’t even begin to compare to what we’re going to see. However, when you start drowning in these applications, does that necessarily mean that these are all going to get used or they’re competitive? No. I think it’s going to break into two kinds of things. First, the best application for a given use case still tends to win the entire category. When you have such a multiplicity of content, whether in videos or audio or music or applications, there’s no demand for average. Nobody wants the average thing. People want the best thing that does the job. So first of all, you just have more shots on goal. So there will be more of the best. There will be a lot more niches getting filled. You might have wanted an application for a very specific thing, like tracking lunar phases in a certain context, or a certain kind of personality test, or a very specific kind of video game that made you nostalgic for something. Before, the market just wasn’t large enough to justify the cost of an engineer coding away for a year or two. But now the best vibe coding app might be enough to scratch that itch or fill that slot. So a lot more niches will get filled, and as that happens, the tide will rise. The best applications—those engineers themselves are going to be much more leveraged. They’ll be able to add more features, fix more bugs, smooth out more of the edges. So the best applications will continue to get better. A lot more niches will get filled. And even individual niches—such as you want an app that’s just for your own very specific health tracking needs, or for your own very specific architectural layout or design—that app that could have never existed will now exist.”