2025 was the most successful year in Tines' history. We tripled our enterprise customer base. We grew headcount by over 50%. We more than doubled the number of automated actions executed on behalf of our customers. These numbers sent a clear message to our team: “keep doing exactly what you're doing, things are going great.”
Instead, we chose to build something new.
Something we know our customers need. Something only a team with eight years of experience powering the world's most important workflows could build.
It's called Tines 3B. And today, after over a year of hard work, we're finally ready to share it.
Tines 3B is our new, AI-native environment for every team's most important agents, apps and automations — built for a world where employees are already building with AI, regardless of whether IT or security teams can see it.
Our existing product Tines, now known as Tines Stories, continues in parallel as our visual designer purpose-built for security and IT operations teams. We're continuing to invest in it, hire for it, and ship new features.
Monitoring in Tines 3B
Building in Tines 3B
Tines 3B, explained
Tines 3B is a single, secure environment for every team's important agents, apps, and automations.
In short, Tines 3B:
Gives every team in your organization the power to build with AI
Gives IT and security the control to run and govern that work safely across the business
You might wonder: why build a new product at all? Why not just add these capabilities to Tines?
Tines Stories has strong AI capabilities and high customer usage, but building something truly AI-native meant starting fresh.
Tines Stories was built on a no-code foundation because in 2018, you got things done by letting a tool handle the code for you. When you describe what you want and ask AI to build it, these kinds of abstractions are unnecessary and cumbersome. LLMs are excellent at translating concepts into working code. That's why Tines 3B needed to be code-first — the opposite of how Tines Stories was designed.
Read the full story of how we made Tines 3B.
The wild code problem
Late last year, I was talking to one of our FinTech customers — a public company with many thousands of employees. They'd just introduced a mandate for AI usage across the entire organization. Everyone was encouraged to use AI to build more, move faster. And it was creating incredible innovation. But it was also doubling the number of security incidents their security and IT teams were dealing with.
Employees were sharing API keys, uploading data to unsanctioned services, all without understanding the risk they were creating. There was nothing malicious about this activity. These people were doing exactly what they'd been asked to do. The problem was that there was no controlled, governed way for them to do it.
We call this phenomenon wild code, because of how it takes root, spreads, and threatens to introduce risk, blow through AI budgets, and overwhelm the teams responsible for keeping enterprise systems safe. And the data backs it up - according to IBM, 77% of organizations report that AI adoption is already outpacing their governance capabilities.
I've lived through several major technological shifts, but this one feels like the fastest-moving. And potentially the most difficult to navigate.
A memo to all employees won't fix it. Locking down tools isn't working. AI councils and steercos add complexity without offering real control.
What organizations actually need is an environment where wild code is never given the opportunity to take root, where IT and security can shift from blockers to enablers, and where every team's work has a chance to thrive. That's the problem Tines 3B was built to solve.
To you who deal in uncertainties
The CIOs and CISOs I speak with aren't just looking for another tool. They're looking for a way to say yes. Yes to their teams building with AI, without losing visibility into what's running in their environment, watching AI spending spiral, and inheriting a sprawl of one-off apps that someone has to maintain, patch, and untangle when a dependency breaks. All of this is overburdening teams that are already stretched thin.
Right now, most of them can't say yes. And yet there’s huge pressure to enable every team, from legal to HR to revenue operations, to innovate with AI.
What technology leaders need is an environment that gives all of those teams a safe, governed path to build, and gives IT and security the visibility to stay in control. That's exactly what Tines 3B provides.
Like many IT teams, we think carefully about the governance challenges that come with AI — security risks, rising costs and shadow AI.
3B's governance and monitoring capabilities, including strong credential protection and access controls, were central to our decision to deploy it.
We're a few weeks into our rollout and already see 3B becoming a critical part of how teams build at Fin.
Emanuele Sparvoli, Senior Director of IT, Fin (formerly Intercom)
Early indicators of success
We didn't build Tines 3B in isolation. Wild code is a relatively new problem, but the underlying challenges are the same ones IT and security have been grappling with for decades. Every assumption we made, every decision we took, was shaped by eight years of conversations with customers who are already using Tines Stories to build intelligent workflows.
A small group of those customers and design partners also worked closely with us to shape Tines 3B, helping us ensure it would deliver meaningful value fast.
One of the most memorable moments has been watching a large investment bank's finance team — people with no technical background — pick up Tines 3B and start building almost immediately. Before Tines 3B, there was no safe, governable path for them to do that.
It's also been incredible to see the same transformation happen inside our own company in just over three weeks. In that time, over 500 employee-built apps, agents, and automations have gone live — most built by people who'd never written code before, all with IT and security oversight from day one. Teams are shipping everything from procure-to-pay workflows and brand asset repositories to sales forecast dashboards and account research tools — meaningful, time-saving builds that just weren't possible before we rolled out Tines 3B.
Some of our design partners have already signed on as Tines 3B customers. I can’t wait to share their stories with you soon.
To our customers
We have earned your trust over eight years by being the company that takes security seriously when others cut corners. We built Tines 3B as a direct response to your feedback.
For our existing customers, nothing changes. You'll continue to have full access to Tines — now called Tines Stories - and the same level of service and support you're used to. We're actively investing in Tines Stories and currently hiring new engineering talent to work directly on the platform. There's no need to change how you use Tines Stories.
That said, we hope you’re curious about Tines 3B, and we’d love to hear your thoughts. That's why all existing customers can explore Tines 3B at no additional cost.
If we've done our job well, many Tines Stories customers will choose to migrate to Tines 3B or adopt it alongside Tines Stories. You know your team’s needs best, and we'll support what makes sense for you. If you have questions, you can reach out to your account team or email me directly at eoin@tines.io.
You didn't choose Tines because we stay in place. You chose us for our pace of innovation and our reliability. Tines 3B is an extension of that commitment.
What’s next
We're so excited to see how customers use Tines 3B to become wildly successful, and to share those stories with you.
None of this would be possible if it weren't for our customers, users, community, investors, and partners - thank you. Your belief in what we're building means everything, and we don't take it for granted.
And to the Tines team: thank you for always running towards hard problems. As we often say around here, it’s fun because it’s hard.