Tines 3B - The secure environment for agents, apps, and automations

One very cool piece of inspiration on the site is the Examples Gallery. Some great real-world examples in there that help give a taste of what can be done on 3B, and can quickly be built out and run on the free Explore offering.

Just describe what you want, and pretty soon you have something that works. But what about what happens next?

This is the part that scares me as a non-traditional builder. I want to build, and learn, but I don't want to put myself or the company at risk. Thankfully, now I don't have to.

It has been such a blast to build in Tines 3B so far - and so easy. Was just looking through my workflows this morning and it's wild (but not wild code!) what I've been able to do so far.

I am entirely too excited to see what others get up to with it!

I have been loving Tines 3B! I come from a somewhat technical background, so I’m used to thinking about all the APIs, webhooks, and code behind these workflows. Being able to focus on what I actually want to build and let Tines 3B handle the technical heavy lifting makes going from an idea to something genuinely useful feel ridiculously fast.

I have loved how Tines 3B is the kind of product that enables you to just go and do things without needing to worry about the technical aspects or wondering if your credentials are secure.

Hey @joseph_parker3! In the age of AI, it’s more important than ever to keep credentials secure.

In 3B, credentials are injected at runtime by a proxy that lives entirely outside the code executed by workflows. This ensures that neither users or LLMs ever read secrets directly, mitigating the risk of runaway workloads or leaked secrets being persisted in context.

It’s also super important to us that users can understand and reason about how credentials are used in workflows. This can easily be viewed in the usage graph for every credential you configure in the product!

Check out our free Explore offering for any testing you’d like to conduct. See you in the product!

@hamza_afzal_butt while I don't have or manage teams to have personal experience, it seems like an organization cam have a centralized owner for 3B, and then each department or team can have their own subset group access. So everything built within will be accessible and manageable to the group above and centralized across the full organization using it.

@hamza_afzal_butt That's a big part of the core value proposition of 3B. The main area that helps manage that in Tines 3B is our monitoring dashboard. It enables the tenant owner to have visibility across all the automations, apps, and agents across the different departments using it.

In Tines 3B, everything rolls up into a space (think:team), so you can see what each department is doing. In the dashboard:

• There are dedicated breakdowns for executions, active workflows and storage by space.

• Failing workflows surface automatically.

• Duplications and dependencies are visible for identifying similar workflows or different workflows with the same dependency.

• You can spot risky exposure by identifying workflows with public or weakly-authenticated endpoints.

• Cost and AI usage are tracked.

For more info, you can get an overview of the monitoring dashboard here in our docs.

@zmiro I love that bit too. I've also been so amazed by how Tines 3B is able to troubleshoot on its own. If it's having a hard time with the first plan of connection, it doesn't give up and put it back on me to figure out.

What have you built so far?

@charles_eric3 You've hit on one of the key patterns we kept seeing. Six months later a credential has expired, the person who built it has moved teams, and nobody notices it's broken until someone complains.

That's a big part of what Tines 3B is for. Everything you build sits in one place with an owner attached, full logs and an audit trail, and the credentials are held by the platform rather than pasted into a script. IT and platform owners get one view of everything running across the business, so an ownership gap gets picked up before it turns into an outage rather than after. If a step does fail, autofix reads the error, applies a fix on a separate branch, reruns it to check the fix actually works and then emails you. Your live workflow isn't touched until you approve it.

So that “little internal tool” stops being a brittle, personal side project and becomes something the org can run.

@charles_eric3 'small software' is a term I've heard used for these tools. In the last month, Tines' marketing team has built over a dozen production apps that we are using every day.

@danielle_swans I can totally relate! 3B has unlocked opportunities for me to build workflows I've always thought about but couldn't instrument myself. As a non-technical user, 3B is really a game changer and I get to build in a safe environment I know our IT team trusts.

@hannah_mccabe And what's extra wild is that YOU were able to do it, right? I am no coder outside of some front end dev stuff, but the things I've been able to do is just wild. Gamechanger for sure!!

@hannah_mccabe That’s what I’ve found most interesting too. I come from a somewhat technical background but I’m blown away by how quickly I’ve been able to get powerful, meaningful workflows up and running with Tines 3B, without ever having to touch the code. That’s what makes it such a gamechanger for me.

@hannah_mccabe I have never seen a tool that really empowers the ability for people to just go and build things like 3B does. I have yet to come across something that I can't do with it.

@sansa_grey Agreed. There has to be that balance between letting it run wild and completely blocking the organisation from building and running workflows with AI.

I personally view that latter scenario of completely blocking it as the worst case. Those competing with you are going to use it. And your employees are going to want to access it and the value it can unlock for them (and the org), and if you don't enable that they'll go elsewhere.

@sansa_grey that's exactly right! We've found that teams across the org want to build and innovate with AI. Tines 3B gives IT teams the confidence and control they can enable that securely.

@sansa_grey This is probably my favorite bit of Tines 3B. I have had so many ideas bouncing around my brain and I'd been long blocked by not only "How do I build this?" but also "Am I even allowed to?"

And now I can. It has totally changed my mindset to tackling problems and I am a happy building nerd over here. :)

@johannes_riecken oftentimes users want to be able to communicate the value that a tool is creating for the team, for example demonstrating that what used to take 10 hours a week for a person paid $50/hr is now happening automatically, and saving $500/week. It's definitely not an exact science, but it's a good way of showing leadership, finance, etc that the investment in a tool like 3B is working out, in a way that doesn't require explaining all of the intricacies of the particular use case you're solving. So this is less about revenue generated, and more about time or money saved.