Tines 3B

@Tines 3B has changed the way that our RevOps team works. Every use case is now solvable in a smart, secure, intuitive way.

Curious as to why you named it 3B. I thought Tines for was releasing a small language model at first lol.

@rosie_halpin is doing a live demo of Tines 3B on LinkedIn and Youtube right now for anyone interested!

I didn't quite understand the part about seeing the revenue generated by each workflow. Is that for entrepreneurs who create lots of small products that they bill independently?

As a marketer I've truly never experienced something like Tines 3B - connecting 3 totally different, unrelated systems to get an accurate picture of campaign performance, spend, and pipeline has been a GAMECHANGER.

@Tines The credential proxy answers above cover the read path well, so I'll ask about autofix instead. It was mentioned it applies a fix on a branch and then reruns the workflow to confirm the fix actually works. If the failing step was a write, posting to an API or sending mail, does that rerun hit the real connector with real credentials, or is there a dry run path so a fix attempt can't duplicate a side effect?

@steobrien This looks really impressive! I especially like the idea of keeping agents, apps, and automations in one secure and auditable environment.Good luck guys!

The credential isolation makes sense, but I’m still not clear on how the actual workflow is controlled. If AI-generated code can request credentials through the proxy, what prevents it from using those credentials to do something unintended? Is there granular control over what each workflow can access or do?

I love how 3B made it easier for me to build any workflows I have in mind without the need to know about technical stuff like APIs or webhooks.

Tines 3B is such an exciting launch for me! I've gone from needing a fair amount of support when building, to being able to build fully functioning workflows myself. The blocker now is knowing what I want to build next 😅This kind of freedom to experiment and find new ways of working has been really fun, and challenging, but one I'm delighted to have. Not being the most technical person, I'm also super happy to still have guardrails up so I'm not just pushing code out into the universe! I'm not blocked from building, but pushing a workflow live is still something that the IT and Security team have visibility over.

The credentials never reaching the AI/code itself is probably the part I'd want to test first.

How are teams handling ownership when lots of small AI built automations start spreading across different departments?Congrats team!

This feels especially relevant for the little internal tools people build with Claude/Cursor and then somehow end up on six months later.

I like that you are not trying to stop people from building with AI. the safer approach seems to be letting them move fast, then putting guardrails around what actually runs.

Hey Product Hunt! Stephen here, Head of Product at Tines, and one of the makers of Tines 3B.Last year, AI coding tools got good enough that anyone could build agents, apps, and automation fast. Just describe what you want, and pretty soon you have something that works. But what about what happens next? AI-generated software needs to connect to the real world, and it often does that by hardcoding API keys in plain-text files or databases. Handing credentials to models that can hallucinate or fall for prompt injection is a major risk. Run that code in a typical, unisolated container, and one bad step can contaminate the whole system.We call this phenomenon wild code: it’s work that’s built fast with AI but runs ungoverned and unmonitored, while creating hidden security, financial, and operational risk.With 8 years of intelligent workflow experience in supporting customers like Reddit, Coinbase, and Databricks, we knew how to solve this problem. And so we set out to build Tines 3B. What is Tines 3B?A single, secure environment for everyone’s most important agents, apps, and automation. Tines 3B provides: Freedom to build with AI anywhereControl to run and monitor that workAn AI-native, code-first platform built to work with LLMs and AI coding toolsWe built Tines 3B with safety as a north star. The AI never sees your credentials. They are injected at runtime by a proxy that sits entirely outside the code.Why launch on Product Hunt now? We recently introduced Explore Edition, a no-commitment way to try Tines 3B yourself. This community of innovators is exactly who we want exploring it first. You’ll have unlimited users, spaces, and connectors, and can push 3 workflows live. This includes tunneling into your own home network or self-hosted services, no port forwarding required. Build, run and monitor your apps, agents, and automation with credential protection, isolated execution, and full auditability.Who is Tines 3B for?Builders who want to go from ideas to workflows using natural languageIT and Security teams who need visibility into what’s running Anyone dealing with sprawl from AI-generated scripts, agents, and one-off toolsInnovators who want AI to write the code for their projects, home labs, or personal agentsWe’d love your feedbackWe think you’re going to enjoy building in Tines 3B, and feel the control it gives you. Powering the world’s most important workflows is what we’re here to do, and we want to know what you think.We welcome feedback from this community on how you and your teams are managing AI-driven work, and where Tines 3B fits in your day-to-day. I’ll be in the comments all day, ask away!