Private preview · Powered by AI

A new kind of online collaboration.

Shared documents changed how teams write. loop changes how teams work: one space where your whole team and its AI agents move the same work forward, in real time.

No code yet? Get on the list.

How a loop comes together
01

Define context

Tell the space what your team is working on. It carries that context across every run, for everyone.

02

Attach capabilities

Give it the skills the job needs, scoped to only the ones you grant.

03

Connect your tools

Slack, Google Workspace, Microsoft 365. It acts in the real tools, not a copy.

04

Automate

Describe what should happen and when. You get a real, inspectable automation.

05

Own the outputs

Every result is a durable file in a workspace you can export. Nothing is trapped.

Shared work

Nobody waits on the one person with the context.

Collaboration has always stopped at the document. Here, what you share is the work in progress: teammates appear live inside a running job, anyone can add a message to it, and speaker labels are preserved so it's clear who said what. When the work needs an answer, whoever is free gives it.

  • A blocked run gets unblocked by whoever's around, not just whoever started it
  • Everyone works from the same run, so nobody re-explains context or duplicates work
  • Presence and a shared activity feed mean you always know who changed what
workspace · who's here
SASarahEditing
KEKendallViewing
KJKenjiViewing
Shared momentum

The work carries on after the room empties.

Collaboration that only happens while everyone is online is just a meeting. Work in loop runs in the cloud rather than in anyone's browser tab, so it continues overnight, over the weekend, and across time zones. The results are in the thread when the team comes back, even if every laptop was asleep.

  • Your morning brief is written before anyone logs on
  • Long jobs finish overnight, so the results are waiting rather than queued
  • Knowledge compounds: what the team worked out yesterday is still there tomorrow
Morning Digest · 07:30
Read 41 unread across mail, chat, calendar
Writing your summary…
Email it to the team at 07:30
Shared routines

Set the routine once, and the whole team owns it.

Describe what should happen and when, and it becomes a real, scheduled routine your whole team can see and edit, not a script on one person's laptop. It opens in a visual canvas, and fires on a schedule, a webhook, a connector event, or a Slack or Teams @mention.

  • Recurring work like reports, digests, and follow-ups stops eating anyone's week
  • Routines belong to the team, so they don't leave when the person who built them does
  • Triggers on a schedule, a webhook, a connector event, or an @mention
Workflow Studio
Every morningRead inboxesSummarizeEmail teamPost to Slack
Shared tools

It works where your team already works.

Your team keeps the tools it already has. Connect Slack, Google Workspace, and Microsoft 365, and loop acts inside them: it sends the real email, replies in the real thread, and edits the real document. On day one it reviews what you've connected and writes a briefing on your projects and stakeholders, so it's useful before anyone configures anything.

  • The follow-up gets sent, not just drafted. No copy-paste step in between
  • Your real Word, Excel, PowerPoint, and PDF files come back edited, not re-created
  • Meetings come back as clean, speaker-labelled notes nobody had to take
Discovery · connected tools
Slack replied in #q3-planning
Gmail sent the follow-up, threaded the reply back
Excel updated the model in place
Call placed on your behalf, commitments logged
Shared software

The tool your team keeps asking for, built by your team.

Describe the internal tool your team wishes it had and loop builds a real, installable app. No engineering backlog, no ticket queue. Publish it to your company catalog so anyone can install and run it, with review, permissions, and versioned changelogs built in.

  • It arrives this week instead of next quarter, and nobody files a ticket
  • Permissions, audit, and review are on by default, without anyone asking
  • Publish once; anyone in the company can install it from a shared catalog
Project Tracker
SAKEKJ
W1W2W3W4W5W6
Discovery
Design
Build
Launch
SAKEKJ
Shared · v4 · installed by 18
Who it's for

See what loop does for your team.

The same space, shaped around how your team already works together. One moment from each.

Security & governance

Secure, sovereign, and never trained on.

Your data stays yours. loop runs on open-source models in an environment you control, so your work is never used to train anyone's model, not ours and not a third party's.

Open-source models

Run on open models you can inspect and self-host, with no black-box dependency on a single vendor.

Never trained on

Your content, files, and outputs are never used to train foundation models. Not now, not ever.

Sovereign by design

Data stays in your environment and region, isolated per workspace, with an immutable audit trail.

Bring your team into the loop.

A new kind of online collaboration, currently in private preview. If you have an access code, come in. If not, leave your email and we'll open the door as we widen access.

No code yet? Get on the list.