The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Built a Bring-Your-Own-Key AI agent platform in Python: clients connect their own provider API keys, so the platform never holds or pays for them.
It ships with an encrypted key vault (per-tenant, with rotation), a model router with per-call cost tracking and a global kill switch, a code-building agent that works inside isolated Docker sandboxes, and a WhatsApp control layer on Meta's official Cloud API with a full audit trail. There is also a research pipeline that verifies claims before they reach an article draft.
204 automated tests, all green. One command deploys it.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Someone asked for a tool like yours on Reddit an hour ago. Did you see it?
Riffle finds buying conversations so you can be the answer.
Waitlist open: rifflehq.com
Nice design
Halvkoppling Trafikskola: a driving school in Stockholm whose only instructor can't touch his phone during eight hours of lessons a day, and learners who write to him in those hours wait until evening for a booking. Halvkoppling is Swedish for the clutch's biting point.
Emil Berg teaches from 08:00 to 18:00 in Hägersten-Liljeholmen and reads messages at 12:05 and after 18:00.
In the demo video, Maja writes to him at 10:07. By hand, her booking took Emil 9 steps, 7 messages and 20 minutes, and she was booked at 19:07. With the chat it took him no steps and no messages, and she was booked at 11:53, when her dad paid from her plan link.
A learner books in WhatsApp, or in the web chat at the Live link below, and starts with one message. Lovable AI reads the test date, gearbox and courses, and the chat asks the rest with taps.
The chat offers two plans sized to the test date, with every lesson dated in Emil's free times, at least two days apart and all before the test. The learner pays with Stripe, or sends the plan to a parent, who pays from a link with no account. The learner's chat then shows DU ÄR BOKAD ("you're booked").
At 12:05 Emil opens his view and handles only what needs him: a test within a week to approve, a lesson log to save, or a question the chat couldn't answer, with a reply Lovable AI has drafted from the school's facts, or a line that he answers it at the first lesson. Send reply puts his answer in the learner's chat, and his approval reaches the learner in WhatsApp with a Pay button. His view also counts the time the chat saved over the last 7 days, at 20 minutes a booking, 2 minutes a message and 15 minutes a refill by hand.
Confirmations, a parent's receipt and reminders with Confirm and New time go out on their own, and moving a lesson takes two taps. The slot it frees goes at once to the learner with the nearest test who has no lesson that day.
Built in Lovable with Lovable AI, Lovable Cloud, App emails, a Cloud Job for the reminders, Stripe and the WhatsApp Business connector.
Live: https://halvkoppling.lovable.app (no login; pay with the Stripe demo card)
Owner demo: View as Emil in the dashed DEMO bar
Wow! The WhatsApp integration is so cool! 👌 I didn't know that was possible with Lovable
Problem: Apps need a secure, organized backend to handle users, orders, products and AI features.
Solution: Built a centralized API Gateway (BFF) in n8n Cloud. One webhook handles validation, API key security and rate limiting, then routes to sub-workflows: Users (register/login), Orders (stock check, totals, status), Products (search), and AI (OpenAI chat, recommendations, review summaries). Supabase is the database.
Tools: n8n, Supabase, OpenAI API, Webhooks
Self-initiated demo project.
I'd test authorization separately for each sub-workflow, especially Orders. Does the gateway pass a verified user identity through, or does the Orders workflow check that the caller can access each order?