Tines
Build agents & automations integrated across your workspace
1.8K followers
Build agents & automations integrated across your workspace
1.8K 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.
Tines
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!
Tines
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.
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?
Hi @mad94! Great question. The step’s code never sees the credentials themselves. It runs in a secure sandbox, and every outbound request must pass through our proxy (internally named Pony). A 3B connector must be explicitly attached to the workflow before it can be used, and the proxy only adds its credentials to requests sent to that connector’s approved URL. Because Pony runs outside the sandbox and a sandbox's networking is routed through Pony, the code cannot inspect, extract, or bypass the credentials. Within those limits, the workflow can perform actions allowed by the connector’s own permissions, so we also recommend using narrowly scoped credentials whenever possible.
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!
This feels especially relevant for the little internal tools people build with Claude/Cursor and then somehow end up on six months later.
Tines
@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.
The credentials never reaching the AI/code itself is probably the part I'd want to test first.
Tines
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!
Tines
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.
Tines
@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.
@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.
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?
Tines
@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.
Tines
@johannes_riecken And the key inputs/assumptions for the ROI estimates for the workflow are fully adjustable, e.g. Hourly rate or time saved. The user/team knows those best so they can adjust them as needed.