Tines
Build agents & automations integrated across your workspace
1.5K followers
Build agents & automations integrated across your workspace
1.5K followers
Tines offers a secure, trusted, vendor-agnostic platform to build, run, and monitor intelligent workflows.
This is the 3rd launch from Tines . View more
Tines 3B
Launching today
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.
Free Options
Launch Team / Built With
Tines
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 anywhere
Control to run and monitor that work
An AI-native, code-first platform built to work with LLMs and AI coding tools
We 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 language
IT and Security teams who need visibility into what’s running
Anyone dealing with sprawl from AI-generated scripts, agents, and one-off tools
Innovators who want AI to write the code for their projects, home labs, or personal agents
We’d love your feedback
We 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!
Tines
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.
Buffup.AI
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.
Tines
@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.
This feels especially relevant for the little internal tools people build with Claude/Cursor and then somehow end up on six months later.
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!