Overview
lowcloud is an AI platform for companies. You do a task once in the chat, provide it to your team as an agent, or let it run automatically as a workflow.
Choose chat, agent or workflow
| What for | What starts it | |
|---|---|---|
| Chat | Doing a task once | Your message |
| Agent | Providing a task to the team | A message in the chat or in Microsoft Teams |
| Workflow | Letting a task run automatically | An incoming email, a schedule, a form or a manual start |
Agents and workflows are in one shared list under Agents. The Quickstart walks through all three once.
Chat
The chat is the start page of the app. Without further configuration, lowcloud Chat answers there, the base chat that every workspace gets automatically. It searches the web, reads web pages and files, and looks up skills. It has no knowledge of its own.
How to attach files and use your connected accounts in the chat is described under Chat.
Agents
An agent is a conversation partner with its own instruction, its own documents, tools and skills. Anyone who may build (the role admin, or the former role developer) can create and change it. A new agent is private. With the visibility Workspace, everyone in the workspace can chat with it.
A skill is a named instruction on how something is done. The agent fetches the full text of the skill when its description fits the task. Under Knowledge there are short rules that apply to the whole workspace.
How to create an agent and share it with your team is described under Building agents and Sharing and access.
Workflows
A workflow consists of a trigger and steps in a fixed order. Each step is an Agent, an Action or a Condition. Publish freezes the draft as a numbered version, but starts nothing. The workflow runs only when a person sets it up for themselves with Set up for me, and then through that person's own accounts. Every execution is a run and ends with a status.
How to build, publish and set up a workflow is described under Your first workflow.
Approvals
By default, lowcloud stops before every writing call and shows the real values, such as the email that would go out. A person then clicks Approve or Reject. Reading calls run straight through without asking. The approval can be switched off per tool.
Open approvals are listed in the sidebar under Approvals. How to answer approvals and questions is described under Approvals and questions.
Connections
Chat, agents and workflows work through connected accounts, such as mailbox, calendar, CRM and file storage. A connection is an account at a service that belongs to one person in one workspace. The catalog contains more than 20 services, among them Gmail, Outlook Mail, Google Calendar, SharePoint, Notion, Pipedrive and HubSpot. The detail area of a service lists in full, under Access rights and functions, what lowcloud can do there.
How to connect a service is described under Connecting services, your own APIs under Custom integrations and MCP.
Processing in the EU
Every selectable model computes in the EU, whether in the chat, on an agent or in a workflow. The model list has two tiers:
- Fully sovereign: the request goes directly to Melious, a German company, without an intermediary.
- European servers: the request goes via OpenRouter (USA) to a data centre in the EU, pinned to an EU endpoint and without fallback to other regions. The models from OpenAI, Anthropic and Google run this way.
You choose a model of the tier European servers explicitly: on an agent, in the chat or as the default model of the workspace. Agents, workflows, documents, conversations, runs and billing are stored in lowcloud's own database. Data from connected services stays with the provider. lowcloud stores only the encrypted access token and fetches the data at the moment of use.
Details are under Sovereignty and models.
Workspace and roles
Everything you create belongs to a workspace, including connections, runs and the credit. On first use, every account automatically gets a personal workspace. Nobody can create further workspaces themselves. The exception is a partner: a partner creates one client workspace per client and builds in it. A workspace holds at most 25 members. People with the role admin build agents and workflows and manage the members. People with the role member use what others have built.
What each role may do is described under Workspace and roles.
Credit
Every workspace is billed against a credit in euros. A new personal workspace receives a one-time starting credit. Anyone with the role admin or the former role developer sees the amount under Settings in the section Credit. If the credit is empty, a running workflow stops with the status Interrupted. After topping up, you continue it with Resume run.
Credit and costs covers costs, topping up and the monthly limit per member.