Codehooks will be a perfect companion for @SnillAI
- Snill has automatic (inbound) APIs w/OpenAPI support
- Snill has outbound webhooks, triggered by custom events and built-in CRUD events
- codehooks can handle webhooks/retries and integrate with other services and update Snill
Building a Snill business database takes a few minutes. You get a safe, rules-based place where you and your AI agents can work together. AI never writes code, it only shapes the data and the rules. You approve it. @SnillAI
Vibe coding makes building software look free.
Until you need hosting, databases, authentication, security, maintenance, and changes that don't break everything.
AI made generating code cheap. It didn't make owning software cheap.
What if business software didn't need custom code at all?
And AI agents were first-class users, just like humans?
https://t.co/EnDcEUFJI0
Updated pricing 🏷️
Now they're more "snill" (🇳🇴 norwegian for "kind") for teams.
Starting at $29/month ($290 yearly) which includes one builder/admin and 5 users.
What's your use case? Build all the internal apps you need now! The free plan is still there to build with.
https://t.co/MHFkftA5xt
There's a lot of talk about AI harnesses right now - and for good reason.
As the models get better, more of the interesting work seems to move to everything we put around them. The tools they can use, the rules they have to follow, what they're allowed to change, and what happens when they get something wrong.
I think the same applies when we use AI to build software.
https://t.co/Mjn2bsRK3f
Snill use cases with prompts, the resulting app and how many seconds it took to build each:
https://t.co/F3gmH86hws
equipment maintenance, staff certifications, IT assets, policy reviews, purchase approvals, complaints, onboarding, inspections, supplier onboarding, warranty claims, time off, IT tickets, change requests, returns, grants offboarding, visitor log and many more.
What we're changing: replica counts and disruption budgets so node maintenance is invisible, a maintenance window outside business hours, and per-dependency health checks so we don't misdiagnose again. Apologies for the disruption.
https://t.co/4rnF68ZIHs is fully recovered. We had two short disruptions this morning, 09:04–10:19 CEST. Here's what happened and what we're changing. 🧵
A routine Kubernetes node upgrade restarted our workloads all at once. While diagnosing, we restarted a shared Redis instance that turned out to be healthy - a missing restart policy then kept it offline for 18 minutes. Both are resolved.
Every integration between two systems drifts, and usually not through any fault in the code. One side was unavailable for four minutes, or a request timed out after the write had already landed, or someone edited a record by hand.
https://t.co/1G5oXbsetU
An enterprise prospect asks whether you support webhooks. The answer decides the deal, so someone estimates the work: fire a POST when something happens. A week, maybe less.....story continues 👇
https://t.co/kAN5ZKM8lE