Tines 3B - The secure environment for agents, apps, and automations
by•
Tines 3B is the single, secure environment for your most important agents, apps, and automation. Build with AI, from anywhere. Code runs isolated and credentials stay protected. Everything you ship is fully auditable and monitored from one place. Tines 3B is code-first and AI-native, built to help you move fast without compromising on security. Explore Edition is available today and gives you access to 3 live workflows with unlimited users, spaces, and connectors.
Replies
RunEvr
@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!
Tines
@adana Thank you!
@Tines 3B has changed the way that our RevOps team works. Every use case is now solvable in a smart, secure, intuitive way.
@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?
Tines
@clement_avq really great question. Currently, autofix (and the agent generally) will avoid re-running anything with a risk of a side effect, without explicit authorization from the user. Additionally, we are in the process of adding "environmental" connectors. So that you could have (say) a sandbox Salesforce connector used in branches, and a production one used for live. That way autofix, the agent, and human users can run without any production risk.
@steobrien The environmental connector split is exactly the shape I'd want. On today's behaviour though, how does it decide a step carries side effect risk? Method alone doesn't settle it, since a POST to a search endpoint is harmless and a GET can kick off a job on the other side, so I'm curious whether that's a per-connector declaration you maintain or something the model judges from the code at runtime.
Tines
@rosie_halpin is doing a live demo of Tines 3B on LinkedIn and Youtube right now for anyone interested!
Curious as to why you named it 3B. I thought Tines for was releasing a small language model at first lol.
@thedatadavis It's actually quite a wholesome reason. You can read about it here: https://www.tines.com/blog/making-tines-3b/#a-third-baby
@jillian_bejtlich Wholesome, indeed. Thanks