Works Under
saas · 2 signals · 1 source
Evidence
Show HN: Gigacatalyst – Extend your SaaS with an embedded AI builder — Hi HN, I’m Namanyay from Gigacatalyst (link: <a href="https://gigacatalyst.com/">https://gigacatalyst.com/</a>). Gigacatalyst allows sales, CS, and users to build one-off features, so your SaaS can support long-tail customer workflows and engineers aren’t pulled away from the roadmap.<p>When you sell software to large businesses, you realize that each customer needs their own workflow and features. Traditionally, this either means long engineering roadmaps or the customers end up using workarounds.<p>But what if <i>everyone</i> could build their critical missing features just by talking to an AI? That’s what we do at Gigacatalyst. We provide an AI customization layer for your customers, CS team, and sales team to build these missing critical workflows without needing any engineers at all. Think Lovable, but built on top of YOUR platform.<p>We connect to your product's APIs, learn your data model and design system, and let non-technical users build governed apps via natural language - inside your product, under your brand.<p>Here’s what it looks like in action: <a href="https://www.youtube.com/watch?v=_taSpSphH6E" rel="nofollow">https://www.youtube.com/watch?v=_taSpSphH6E</a><p>One of our customers, a Series B company, saw their users (<i>not engineers</i> - managers, ops people, facility directors) build critical workflows like:<p>- Parts stockout prevention: A maintenance manager typed <i>"show me which parts will run out in the next 2 weeks based on usage over the last 90 days, accounting for vendor lead times."</i> The app tracks consumption velocity, forecasts stockouts, and alerts before it's too late. He says it's prevented ~$500K in emergency downtime.<p>- Invoice OCR from phone photos: Technicians kept losing paper invoices. The prompt: <i>"upload a photo of the invoice, extract vendor name, date, amount, and line items, then match it to the purchase order and flag discrepancies."</i> Now techs snap a photo on-site to automatically add to the system of record.<p>- Restaurant emergency triage: A pizza chain's facilities manager was drowning in maintenance requests. He built a priority matrix: "walk-in freezer not cooling" auto-routes as CRITICAL, "dining room light flickering" goes to LOW. He's now able to manage backlogs with the correct priority.<p>How Gigacatalyst works under the hood:<p>1. Agentic API discovery: Our agents go through your app and parse your endpoints, query params, request/response shapes, and sample data to build the base layer.<p>2. Generation and Validation: When a user describes what they want our AI generates an app. We set up multiple validation steps, including static checks, runtime error analysis, and LLM-as-a-judge.<p>3. Sandboxing and Compilation: We wrote our own compilation and sandboxing framework to get the fastest speeds and lowest costs. This means that users can interact with the built app in seconds.<p>4. Proxy layer: We create a proxy layer for all APIs to handle auth, tenant isolation, and rate limiting. Everything the agent has access to is controlled, logged, observed, and version controlled.<p>After 2000+ daily users, 900+ apps built, and 70% 30-day retention, today we're opening a public demo.<p>Try it: <a href="https://app.gigacatalyst.com/">https://app.gigacatalyst.com/</a> - enter your SaaS product's API URL (or just the homepage) and start prompting.<p>If you're serving a variety of use cases, you probably deal with a lot of custom requests and Gigacatalyst will save you time and increase your bottom line. Book a meeting at <a href="https://gigacatalyst.com/#contact">https://gigacatalyst.com/#contact</a> and I'll help your team and customers build new functionality on top of your platform.<p>I've been reading Hacker News since I was 12 years old. I'm proud to launch for all of you and I want to hear your feedback on my product and comments!
Show HN: AI that trades speed for reliability in site generation — I run a small agency and we’ve been building client websites for years. The work is hands-on, repetitive, and time consuming. We tried platforms like Replit and Lovable, but the output didn’t hold up for production use. Things were missing, editing was limited, and reliability was an issue. Out of that frustration we built Zylo, an AI platform that generates production-ready web apps. It is not instant like Lovable (our builds take roughly 15 minutes on average depending on complexity) but we focused on completeness and reliability instead of speed. What Zylo does Generates full stack Next.js projects including frontend, backend, and database setup<p>Built-in domain management so you can bring your own or purchase directly inside Zylo<p>E-commerce system that feels like a lightweight Shopify with product management and categories<p>Stripe integration through API connection for payments<p>How it works under the hood You interact with an AI chatbot that coordinates several agents following the same processes we used manually when building sites<p>Agents generate code, proofread, and check for missing assets or design issues<p>Any build, runtime, or TypeScript errors are automatically caught and repaired before deployment<p>A final agent handles production deployment and gets the project hosted and ready for a domain connection<p>Editing We put a lot of effort into the editing side. There is a live Monaco editor that renders the site. You can click directly on any component, section, or entire page and pass that as context back to the agents for regeneration. This was something we found lacking in other tools and wanted to solve. What’s next We are currently working on a visual workflow builder. Think of something similar to GoHighLevel’s UI, but instead of manually wiring things, the AI fills in the code and functionality behind the scenes. The idea is to let people map out flows visually and have them actually run in production. We would love feedback from the HN crowd. The big trade-off we made is slower build times in exchange for more complete and reliable projects. Do you think that trade-off makes sense, or would speed always win out for you?