Articles
Practical guides on no-code MCP servers, usage-based billing, agent memory, and shipping AI features without a backend team.
- Engine teardown, chapter 1: How AppElixir compiles a form into an MCP server
- Engine teardown, chapter 2: Forms become tool inputs, collections become tool outputs
- Engine teardown, chapter 3: One collection abstraction over spreadsheets, SQL, and REST
- Engine teardown, chapter 4: Inside the generated MCP runtime
- Engine teardown, chapter 5: Tool ergonomics, descriptions an LLM will actually call
- Engine teardown, chapter 6: The security plane (auth, rate limits, audit)
- Engine teardown, chapter 7: Deploy or self-host, one MCP artifact, two runtimes
- How Lovable credits actually work (and how to not burn through them)
- AI app builder comparison 2026: Lovable vs Bolt vs v0 vs Replit Agent
- Supabase Row Level Security for vibe coders: the one thing AI gets wrong
- Your vibe-coded app got users: what breaks first (and how to survive traffic)
- Do you actually own your AI-built app? Lock-in, code export, and getting out
- AI features in no-code apps: where does the agent memory live?
- AI prompt cost control: the soft cap that saves your margin
- Bubble's Workload Units Are Eating Indie Hackers in 2026
- Build an MCP Server in 5 Minutes (No Code Required)
- Building an embedded customer usage dashboard customers actually open
- EU data residency for no-code apps: when 'in the EU' is a contract clause
- HIPAA for solo SaaS makers: the checklist that gets you a BAA
- Internal-tools builder vs Rails/Django: where the line actually runs
- The database your no-code app actually wanted: KV vs spreadsheet
- MCP Security Checklist for No-Code Builders (2026)
- MCP Server for Agent Memory: Give Your Agent a Persistent Brain
- MCP Server for Usage Billing: Let Your Agent Read Customer Spend
- MCP vs ADK vs LangChain Tools: Which Should Your Agent Speak?
- From no-code to usage-based billing: a maker's guide to metered pricing
- On-demand usage vs flat monthly: the Cursor model and when it fits
- Pricing for high-COGS side projects: when flat monthly breaks
- Self-hosted no-code: when 'we run it ourselves' is the only acceptable answer
- Stripe metered billing for makers: the pipeline that doesn't break
- Three meter models compared: hard cap, soft overage, credit packs
- Turn a REST API Into an MCP Server (No Code, 2026)
- Validate a no-code app idea before you build it: a weekend playbook
- The vibe-coding security checklist to run before you launch
- When to graduate from no-code: 5 signals you need a real backend