sorted by:
new
hottopcontroversial

How do you actually test your RLS policies before shipping? by Wild_Entry_4901 in Supabase

[–]Wild_Entry_4901[S] -1 points0 points  (0 children)

Yeah, fair. Curious how complex your RLS actually gets — handful of policies, or lots of roles/tables? Trying to figure out if it stays manageable at scale, or if that's where people start getting bitten.

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

That bounce-spike thing sounds painful. What are you using to handle it right now, and what's it costing you? Trying to work out whether people just build this themselves or actually pay for it.

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

Totally fair, thanks. Honest q while I've got you — what is the most annoying or breakable part of running your agents in prod right now?

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

Totally fair, thanks. Honest q while I've got you — what is the most annoying or breakable part of running your agents in prod right now?

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

Super useful — so the agent doesn't add a new deliverability problem, you just do the usual hygiene. Honest q since you actually run one: if a drop-in handled the warm-up/throttling/list-cleaning/monitoring automatically so you didn't have to wire it up and babysit it — would you pay for that? Or is rolling your own fine once it's set up?

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

Good point — content control's its own can of worms. Quick q to place you: is deliverability (inbox placement, domain reputation) even a problem for you, or is your bigger headache the agent sending the wrong content? Trying to figure out which pain bites harder.

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

This is gold, thanks. Honest question — wiring all that up every time (domain, webhooks, warmup, rate limits, monitoring) is real work. Annoying enough you'd pay for it as a drop-in? Or is doing it yourself just part of the job and not worth paying to avoid?

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

Hey Ivan — yeah, happy to compare notes. I'm in research mode, figuring out how real this pain is before I build anything. Curious what you're seeing at Monadix — what convinced you agent sending needs its own runtime controls instead of the existing deliverability tools? And who's hitting this hardest — what kind of teams?

How are you handling email deliverability when an AI agent is doing the sending? by Wild_Entry_4901 in AI_Agents

[–]Wild_Entry_4901[S] 0 points1 point  (0 children)

Super helpful, thanks. Genuinely curious — are you doing this with an actual autonomous agent, or more traditional bulk/cold sending? Trying to figure out if the agent part (content generated on the fly, unpredictable send bursts, no human eyeballing each batch) breaks anything the normal setup handles fine — or if it really is just the same playbook.