We build Rayin the open.
Everything below is running in production right now. Most of it started as something that went wrong while we used Ray on our own team.
Last shipped July 21, 2026
- Billing
Three flat prices, one for each team size
Ray Pro stopped being one price for everyone and became a band that matches your team.
- $49, $99 or $199 a month, flat. The bill never moves because you used Ray more.
- Every band gets every integration and the same model. Nothing is held back for a higher tier.
- Ray counts the people it actually worked with this month, so you land in the right band without guessing.
- Product
Digests report from the live list
Scheduled posts now read the current state when they fire instead of replaying an older summary.
- Your standup digest reflects what the tracker says this morning.
- A cancelled run no longer takes the schedule down with it, so a daily cadence keeps its rhythm.
- Recaps you ask for by hand arrive in the same shape as the scheduled ones: titled rows, real links.
- Product
Ray learned the craft of the work it does
Tickets, email and campaign briefs now arrive shaped the way a good operator would write them.
- A filed ticket carries a problem statement, what was expected, what happened, and acceptance criteria you can check.
- When Ray does not know something, it writes that down instead of inventing it. Reproduction steps: unknown.
- Playbooks load only when a task calls for one, so a quick question stays quick.
- Product
Memory the whole workspace shares
Something your team settles in a public channel is now available to Ray everywhere in the workspace.
- Say it once in #general, and Ray has it when you ask in a DM three days later.
- Anything from a DM or a private channel stays where it was said. Private never leaks into shared.
- Ask Ray what it remembers, or tell it to forget. Both work in plain language, and forget means gone.
- Trust
Privacy, terms and the security posture, published
The three documents that tell you how Ray holds your data went up, with real numbers in them.
- Retention, subprocessors and deletion windows stated as they actually run, not as a category average.
- Uninstalling revokes Ray's access to your tools, tears down its schedules, and queues your data for deletion.
- Reinstall inside the grace window and your workspace comes back exactly as it was.
- Platform
A new brain, and scheduled work that speaks up
Ray moved to a new default model, and a scheduled run that fails now says so instead of going quiet.
- A digest that cannot be delivered posts a notice in the channel. It never fails in silence, and it never bills you for the attempt.
- Text Ray reads out of your tools is handled as data, never as instructions. A line buried in a ticket description cannot tell Ray what to do.
- Work that fails or loops still does not count against your usage. That was true on day one and it stays true.
- Product
Ray reads the room in threads
Two ways Ray used to misread a thread are gone, both found while running our own team.
- A question aimed at Ray gets words back. It no longer answers a real question with an emoji.
- A request naming a teammate ("file this one for Oleksii") is a task for Ray, not a handoff away from it.
- When Ray wakes up in a busy thread it catches up on what it missed before it answers.
- Trust
Change your mind while an approval is pending
Corrections that arrive after Ray asks for approval now land in the work instead of falling on the floor.
- Say "make it urgent" while the card is waiting, and Ray withdraws that card and files the corrected version.
- Approval cards carry the real content: an email's recipient, subject, and the full body, quoted verbatim.
- Once you click, the card keeps its evidence, so the record of what you approved survives the decision.
- Product
Ray remembers what it did
Ray keeps a record of its own work, so you can ask about something it handled days ago.
- "Did Oleksii ever reply?" now gets a real answer, traced from the email Ray sent to the live thread.
- Ray knows which channels it is in and what has been busy, without you re-explaining the workspace.
- It also learned to write like a colleague: fewer words, no filler, no closing sales question.
- Product
Four messages, one answer
Ray waits for you to finish your thought and responds to the whole thing once.
- No more one reply per fragment when you type the way people actually type.
- Correct Ray while it is working and the correction folds into the task in flight.
- "Ray is reading the channel." "Ray is drafting an email." The status is true while it is happening.
- Product
Catch up on join
Invite Ray to a channel and it reads what it missed, then acts on the asks still worth doing.
- The request someone made before Ray was in the room no longer disappears.
- Ray knows what time it is and how old a message is, so a three-day-old ask does not get acted on as if it were live.
- Integrations
Trackers, mail, and things that run on a schedule
Ray got the tools most teams live in, plus recurring digests and one-off reminders.
- Linear, GitHub, Jira, Asana and ClickUp: read what is there, file new work in any of them.
- Gmail: drafts run free, every send waits for your approval.
- "Post a standup digest every weekday at 9" works, in the timezone of whoever it is for.
- Product
Memory, and the approval gate
The two things Ray is built around landed in the same week it started.
- Ray remembers what your team tells it, corrects itself when you correct it, and forgets on request.
- Every sensitive action stops at an Approve or Decline card before anything runs. There is still no setting that turns this off.
- Ray follows a thread, so a follow-up never starts from zero.
- Platform
Day one
First commit. Ray was running in production four days later.
Watch the next one land.
Add Ray to your workspace and put it on something real. The 50 free tasks do not expire.