Your engineering work, in one place with the rest of the company.
TulipFarm is an AI workspace where engineering teams sum up pull requests and issues, draft release notes and keep incident write-ups. Agents help with recurring work, and Support and Product use the same records.
Public beta, open to everyone. Your first signup includes $50 in free credits.
No account needed. The tour runs in your browser and doesn't connect to your accounts.
Where engineering meets the other teams.
Engineering trades work with Support, Product, Security and Operations. Each handoff stays in the same workspace, so the next team picks up the original record.
Coming in
SupporttoEngineering
Bug reports
Support adds bugs to a Bug reports table you share, with the customer's words and the steps to reproduce. A new urgent row can start your triage workflow.
TulipFarm for customer support teamsBack to the mapSecuritytoEngineering
Security findings
Security logs findings in a table you share, with severity, owner and the linked GitHub issue. Ask in chat which findings are still open for the next release.
TulipFarm for security teamsBack to the map
Going out
EngineeringtoProduct
Release notes
Draft release notes from the pull requests merged since the last release and save them in Files. Product turns them into launch notes, so nobody rebuilds the change list from memory.
TulipFarm for product teamsBack to the mapEngineeringtoOperations
Incident write-ups
Write each incident up in Files from the incident's project, with the timeline and follow-ups. Operations reads the same write-up instead of asking for a recap in Slack.
TulipFarm for operations teamsBack to the map
The engineering work that comes back every week.
Bugs and incidents go in tables, runbooks and write-ups in Files, and the recurring work to agents or workflows. Set a job up once in chat, and the next run and the next teammate start from there.
In these examples, Bramble is your team's engineering agent.
PR and issue summaries
When: Any time
Connect your own GitHub account, then give Bramble a task: sum up a pull request with its reviews and linked issue, or list what changed in a repository this week. Bramble reads only the repositories your account can access.
Release notes drafts
When: Each release
Ask chat to draft release notes from the pull requests merged since the last release and save them as a Word document in Files. Chat can also propose a draft GitHub release, and nothing is created until you approve the exact text.
Incident write-ups
When: Each incident
Give each incident a project that holds its chats, logs and notes. Save your write-up format as a skill, then ask chat to draft the write-up in Files for the team to review.
On-call handoff
When: Each rotation
Schedule Bramble to run at the end of each rotation. It reads the Incidents table and drafts the handoff note in a private task for the outgoing engineer to review.
Bug intake from Support
When: Each report
Set up a triage workflow in chat. When Support adds an urgent bug, Bramble drafts a summary and suggests an owner, the run waits for your review, then Slack gets only the message you approved.
TulipFarm doesn't page anyone or replace your incident tools. Any change in GitHub, from an issue comment to a draft release, waits for you to approve the exact change.
One bug report, start to finish.
An example: Sam, an engineering lead, is on call when Support reports that checkout is failing. Here's how the report moves and where he stays in charge.
What the workflow and run statuses mean
Saved
Sam saved the workflow from chat. Nothing runs yet.
Activated
He turned it on. A new row in Bug reports can now start a run.
Run started
Support added the checkout bug, so a run began.
Completed
The run posted the approved summary to #eng-oncall and finished. The bug row stays in the table for the fix and the follow-up.
Set up a workflow: when Support adds a bug marked Urgent to the Bug reports table, have Bramble summarize it, check our on-call runbook and suggest an owner. Check with me before anything goes to #eng-oncall.
- Trigger
Support adds a bug to the Bug reports table: checkout fails for some customers.
New bug: checkout failing - Condition
Checks whether the bug is marked Urgent. If it isn't, the run stops here and the row waits for regular triage.
Passed: Urgent - Agent
Bramble reads the report and the on-call runbook in Files.
Read report and runbook - Agent
Bramble drafts a short summary with the likely area and a suggested owner.
Summary and owner drafted - Review
The run pauses until Sam reviews the summary and responds.
Sam responded - Slack
Posts the summary to #eng-oncall once Sam approves the exact message. Nothing is sent before that.
Approved, sent to #eng-oncall
Completed means the run finished its steps. Check the run history to see what each step did.
What stays after the incident closes.
When someone rotates off call or leaves the team, nobody has to rebuild the context from memory.
- Records
- Bug reports, incidents and security findings stay in their tables.
- Context
- Runbooks, write-ups and release notes stay in Files. Each incident's chats stay in its project.
- Decisions
- Workflow runs and approvals stay in run history, so you can see what was approved and what was sent.
- Procedures
- Skills, saved agents and workflows are ready for the next incident, so a new engineer starts with the same steps.
Questions from engineering teams
What is TulipFarm for engineering teams?
TulipFarm is an AI workspace where an engineering team keeps bug reports, release notes, incident write-ups and on-call handoffs, with agents and workflows for the recurring parts. Support, product, security and operations work in the same workspace, so a bug report or a write-up stays in one place instead of being copied between apps. TulipFarm Cloud is in public beta and open to everyone.
Does TulipFarm replace GitHub or our incident tools?
No. TulipFarm isn't built to replace your code host, CI, issue tracker or paging tool. It holds the work around them: summaries, release notes, write-ups, handoffs and bug intake from Support. You can start with one recurring job, such as the on-call handoff.
What can TulipFarm read and change in GitHub?
It reads, and it changes only what you approve. After you connect your own GitHub account, chat and your agent tasks can read issues, pull requests, reviews, Actions logs and releases in the repositories that account can access. Changes such as an issue comment or a draft release wait until you approve the exact change. Other members and workspace admins can't use your GitHub account.
Can a GitHub event, such as a merged pull request, start a TulipFarm workflow?
No. TulipFarm workflows don't start from GitHub events. A workflow can start from a new issue in a Jira project or a row change in a TulipFarm table, such as a new bug in a shared Bug reports table. For GitHub work, ask in chat or give an agent a task.
Does TulipFarm page on-call engineers or run deploys?
No. TulipFarm doesn't page anyone, and it isn't a deploy tool. It can start or rerun a GitHub Actions workflow only after you approve that exact change, so check what the Actions workflow does before you approve it. If your workspace connects Slack, a TulipFarm workflow can post to a channel after you approve the exact message.
Who can see our incident notes and bug reports in TulipFarm?
Only people you share them with. Private chats and agent tasks are visible only to the person who owns them, and workspace admins can't see them either. Project members see their project's chats and files, and you can share tables and files with the people who need them.
How do I get started with TulipFarm for engineering, and what does it cost?
Sign up for TulipFarm Cloud. The public beta is open to everyone, and your first signup includes $50 in free credits. Public paid plans haven't been announced; see the pricing page to ask for more credits or apply for student, NGO or startup support. You can also take the browser tour, called Explore, without an account; it doesn't connect to your business accounts.
Start with one rotation.
Sign up for TulipFarm Cloud and set up the job you repeat most, like the on-call handoff or bug intake from Support. The public beta is open to everyone, and your first signup includes $50 in free credits.
Want to check your tools first? Contact us about what your team uses.