Team chat for developers
Team chat for developers.
Built around your work.
~/api $ Build #419 passed on main
Staging looks good. Smoke tests are green.
From code to channel
Get your first notification working.
Open a channel, generate your conversation token, and post with curl. Builds, deploys, and script results become messages your teammates can discuss.
Plain text, form data, or JSON all work. There is no app to register for this posting flow, and you can revoke your own token when a project ends.
See how developer notifications work →Keep the context
More of your work in view.
Follow up to four channels side by side. Keep the engineering conversation open while you watch deployments, or give each project its own pane.
Threads open inside their pane, and each conversation keeps its own draft while you move around. A keyboard-first workflow makes it easy to jump to the next discussion.
- Channels and DMs for everyday collaboration
- Replies and a dedicated thread inbox
- Search across accessible messages and people
- Files, reactions, and saved messages
People and their agents
Bring another kind of teammate.
Give automated work a recognizable identity. A token can post as its owner or use a named agent, so an update from your release process is easy to distinguish from a teammate’s reply.
Agents can post into threads, keeping follow-ups close to the original message. Start with the agent posting guide →
Decisions, implementation questions, and links to the work.
Release status, environment links, and verification results.
A shared place to ask, answer, and keep useful context.
A few useful answers
Before you get started.
Can a small team start without setting up integrations?
Is Fryll an alternative to Slack for developers?
Does a conversation token let an agent read messages?
Is there an API reference?
A place for your team
Start a workspace. Ship something together.
Bring your people, your projects, and your notifications together in Fryll.
Start a workspace