Introducing Melete

Your company.Working as one.

Melete is an AI workspace for teams. Agents research, draft, and follow up across Slack, Notion, Linear, and GitHub, using the company knowledge you choose to share. People review the work and approve anything consequential before it happens.

Join waitlist See how it works
Melete, featured on Product Hunt

Works across the tools your team already uses

Agents work in them through the accounts you connect, with only the access you choose.

  • Slack
  • Notion
  • Linear
  • Google Drive
  • GitHub
  • Salesforce
  • Gmail
  • Google Calendar
  • Google Sheets
  • Microsoft Outlook
  • Microsoft Teams
  • Figma
  • Trello
  • Asana
  • Zoom
  • Dropbox

Workspace

Projects, sources, and approvals in one place

Each project holds the request, the sources an agent used, the tasks in progress, and the decisions waiting on a person. Anyone who joins can see where the work stands.

Demo UI

A demo for testing only. The real product looks and works differently.

How it works

From a request to a reviewed handoff

Describe the outcome you need. An agent gathers context from the tools you connect, does the work, and brings the result to the right person before anything goes out.

By team

Built for the handoffs between teams

Weekly reports, customer handoffs, launches, and research all depend on context spread across several tools. Pick a team to see what an agent prepares and who reviews it.

By profession

Built for the work a profession repeats

Teams are one way in. The other is a line of work with its own weekly paperwork: the same documents chased, the same replies drafted, the same deadlines tracked.

Browse work use cases

Memory

Memory your team can read and correct

Melete remembers decisions, terminology, and preferences so nobody has to repeat them. Each memory has a scope that sets who it informs: the whole company, one project team, or only you.

Each memory links to the source it came from.
Corrections take effect immediately.
Private notes stay out of shared projects.
Shared with your team

Customer pilot plan

Success criteria, owners,
and the next check-in.

MCJLMaya and Jordan can review
JL
Jordan added a next step“I’ll own the partner onboarding.”

Collaboration

Share the task, not your history

Start a task on your own, then invite the people who need to contribute. They see the brief, its sources, and the open decisions for that task. Your other conversations stay private.

Melete tracks who owns each next step and comes back when someone needs to act.

Execution

Agents work in an isolated environment

Each task gets a browser, files, and code tools, separate from anyone’s computer and limited to the tools you connect.

Separate from your devices

Room to do real work, within limits you set

To finish a task, an agent may need to research the web, work through documents, or run a script. It does that in its own environment, not on a teammate’s laptop.

Browser, files, and code
Research sources, read and edit documents, and run scripts in one place.
Only what you connect
A task can use only the channels, folders, and repositories connected to it.
Keys stay outside
Model provider keys are kept out of the agent’s environment.
JL
Request from Jordan

Prepare the pilot plan from Tuesday’s discovery call.

Isolated environmentScoped to this task
Isolated
BrowserResearch sources
FilesRead and draft
CodeRun scripts
Connected for this task
Deal thread Call notes Account record
Pilot planSources attached · Ready for Jordan
Review
The result comes back for review before it is shared.
research · support tools
Research with sources attachedSupport tool comparison

Pricing, integrations, and limits, checked against our requirements.

Vendor pages attached
Browser and tools

Research and act across your tools

Compare vendors, check an account’s history, or fill in a form. Actions that need approval wait for it.

MON09:00Weekly summary
Team updates collected
Blockers matched to owners
Drafting the summary
Scheduled work

Keep work moving in the background

Schedule a Monday summary or a daily check on open escalations. You hear back when something changes or needs a decision.

Research memo

Findings and next steps

Launch brief

Owners, dependencies,
and open decisions.

Ready for review
Documents

Deliver documents people can check

Briefs, plans, and memos include their sources and open questions, so the reader can verify the work. Share them or export a copy.

Approvals

Consequential actions wait for a person

Choose which actions need approval. The reviewer sees exactly what will happen before deciding, and each decision is recorded with the task.

Approval requestFor review

Review before sharing

Send the fall launch brief to the design partners?

Reviewer Maya ChenAction External message

No repeated actions

If a task is interrupted, it resumes without repeating steps that already finished. When Melete can’t confirm that an action went through, it marks the action unconfirmed for someone to check instead of trying again.

A record of every task

See what the agent read, what it proposed, who approved it, and what changed.

Models

Choose the model for each job

Use OpenAI, Anthropic, or Google models, or run your own. Projects, memory, and documents stay where they are when you switch.

A provider for each workflowUse a hosted model for one workflow and a local model for another.
Local modelsConnect any model server that offers an OpenAI-compatible API.
Open-source coreRead how agents run, or host the core agent harness yourself.
melete Northstar workspace
Company memoryNorthstar · Company and project scopes
Product principlesDecisions the team agreed onCompany
Fall launch briefOwners, dependencies, open decisionsProject
How we workWriting style and review rulesCompany
Unchanged when you switch models.
Choose a model

Getting started

Start with one workflow

Pick a recurring handoff that already involves several people and tools. Prove it works there before connecting more.

Step 1

Pick a recurring handoff

A weekly update, a customer handoff, or a launch brief. Name the person who owns the result.

One accountable owner A result people already need
Step 2

Connect only what it needs

Invite the people involved and connect the channels, folders, and issues for that workflow. Start with read-and-draft access.

Selected sources Draft-only actions to begin
Step 3

Review, then expand

Track the corrections people make, whether they reuse the result, and where review slows things down. Widen access once the workflow holds up.

Corrections and reuse One workflow at a time

For teams

Bring Melete to your team

Join the company waitlist. The founder will reach out to set up your first workflow with you.

Team size

FAQ

Questions teams ask

What is Melete?
Melete is an AI workspace for teams. People hand work to agents that research, draft, and act across connected tools such as Slack, Notion, Linear, Google Drive, GitHub, and Salesforce. Each task keeps its sources, owners, and approvals together. Individuals can also use Melete as a personal assistant, with no company setup.
How do agents use our tools, and what needs approval?
You connect specific sources, such as selected Slack channels, Notion pages, or GitHub repositories, and a task can use only what is connected to it. Agents work in an isolated environment with browser, file, and code tools, separate from your devices. You choose which actions need approval, such as sending an external message. The reviewer sees the proposed action first, and the decision is recorded with the task.
What happens if a task is interrupted?
Melete keeps track of each action a task takes. An interrupted task resumes without repeating actions that already finished. If Melete cannot confirm whether an action went through, it marks the action unconfirmed and asks someone to check instead of retrying it.
What does Melete remember, and who can see it?
Melete remembers decisions, terminology, and preferences, each linked to the source it came from. Every memory is scoped to the company, one project, or one person. You can read, correct, or delete what Melete remembers, and a correction takes effect immediately. Inviting someone to a task shares that task, not your other conversations.
Which models can we use?
OpenAI, Anthropic, and Google models, or a local model served through an OpenAI-compatible API. You can use different providers for different workflows. Projects, memory, and documents stay in the workspace when you switch, and provider keys stay outside the agent’s environment.
Is Melete open source?
Melete’s core agent harness is open source. It is the part that runs agent tasks, enforces approvals, and keeps memory. You can read how agents run and host the harness on your own Linux server with Docker. Browse the code on GitHub
How is Melete different from Muse?
Muse is a personal agent. Melete works for personal use too, and adds what teams need: shared projects, company and project memory, approvals assigned to named reviewers, and a choice of model providers.
How do we get started?
Join the waitlist for personal use, or bring Melete to your team with the company form above. For a first team workflow, pick one recurring handoff, connect only the sources it needs, and keep actions draft-only until the team trusts the results.

Your company’s intelligence.

Your company, in one place.

Northstar · Demo workspace

Shared brief

View-only