FAQ
How is Linkworld different from OpenClaw?
Section titled “How is Linkworld different from OpenClaw?”Same heartbeat / multi-agent / group-rooms primitives. The differences are in the deployment model:
- Multi-tenant SaaS — your team shares a tenant rather than each running their own self-host
- EU-sovereign hosting — data stays in EU regions
- Multi-LLM routing — Anthropic, OpenAI, Google, Mistral; the platform routes per-call so cost can be 10× lower for routine heartbeats (Haiku / 4o-mini / Flash)
- Vision-loop for strategic agent autonomy (multi-phase ASSESS → DEBATE → PLAN → EXECUTE → REVIEW) — not just heartbeats
- Approval queue, audit log, security gate built in for compliance use
- Packaged industry apps (Office Assistant, Sachverständiger, Marketing War Room) ready to install
OpenClaw is the better choice for personal-productivity self-host; Linkworld for businesses that need governance, multi-LLM economics, and pre-built apps.
Is my data really staying in the EU?
Section titled “Is my data really staying in the EU?”Yes by default. The platform’s primary deploy is EU regions; tenant databases, audit logs, agent memory, and uploaded files all sit in EU infrastructure. Cross-region replication is opt-in.
LLM provider calls go to the provider’s infrastructure (Anthropic US, OpenAI US, Google EU, Mistral EU). The platform doesn’t automatically choose EU-only — you configure your tenant’s LLM provider preference. If EU-only routing matters for your use case, choose Mistral or Google’s EU regions in the tenant settings.
How much does it cost to run heartbeats?
Section titled “How much does it cost to run heartbeats?”Depends on the model tier you pick — a cheap tier costs a small fraction of a frontier one for the same routine.
What keeps the bill predictable is the pre-filter: most ticks decide mechanically that there is nothing to do and never reach a model at all. You pay for the ticks that had something to think about. The audit log captures per-call tokens so you can see costs in detail.
Can I trust an agent to act on my behalf?
Section titled “Can I trust an agent to act on my behalf?”Three layers of protection:
- Manifest declarations — apps must declare what they can do at install time. Adding a new tool requires a new app version and your re-approval.
- Bilateral grants — cross-app calls require both apps’ admins to opt in. The Steward can’t reach across the tenant automatically; you set up each pairing explicitly.
- Approval queue — destructive / sensitive actions surface as approval rows you sign off on individually.
You can run agents as fully-autonomous (skip the approval queue), fully-supervised (every action requires approval), or anywhere between (per-tool approval policy). Default is supervised — deliberately conservative.
What happens if an agent goes haywire?
Section titled “What happens if an agent goes haywire?”Three brakes:
- Auto-disable on failure — heartbeats with 5 consecutive failures auto-disable. Failing earlier shows up on the Health screen.
- Pause an app — Workspace Control → app row → Pause stops all heartbeats and disables the agents while keeping memory intact.
- Revoke a grant — wires & grants editor, click Revoke. New cross-app calls denied immediately.
Can the same agent run for multiple users?
Section titled “Can the same agent run for multiple users?”Agents are tenant-scoped, not user-scoped. One tenant’s agents are isolated from another tenant’s. Within a tenant, all users share the same agent set (the agent’s memory is shared, the conversation is per-user).
If you need per-user isolation within a tenant (rare), the recommended pattern is multiple tenants — invite-based, each user runs their own. The platform supports this; your billing scales with active tenants.
Can I export my data?
Section titled “Can I export my data?”Yes. As tenant admin:
- App records: per-app export from the app’s UI (or the bulk
export endpoint at
/api/admin/records/export) - Audit log: time-range export from the Audit screen (“Export CSV / JSON”)
- Conversations + memory: per-user export from the user’s profile menu
- Full tenant export: contact support for a tenant-wide bundle (usually within 24 h)
All exports are JSON-Lines or CSV, machine-readable.
What about retention?
Section titled “What about retention?”Default retention windows:
| Data | Default |
|---|---|
| Audit log | 365 days |
| Approvals | 365 days |
| Agent memory | indefinite |
| Conversations | indefinite |
| Records | indefinite |
Configurable per tenant within legal limits. Beyond default windows, archived data lives in cold storage.
Can I host Linkworld myself?
Section titled “Can I host Linkworld myself?”No — the platform is hosted SaaS, operated EU-sovereign under our control. There is no self-hosted or airgapped edition today.
If EU jurisdiction is what you need, that is already the default: your data is processed in the EU, is never used to train a model, and every model choice is logged. See Audit & compliance.
How do I report a security issue?
Section titled “How do I report a security issue?”Email [email protected]. PGP key on the website.
For non-security bugs: GitHub issues at the examples repo.
Where do I find my tenant ID?
Section titled “Where do I find my tenant ID?”Workspace Control → Health → “Tenant” in the page header (or URL slug). When opening support tickets, include the tenant ID + the timestamp of the issue.
Why doesn’t agent X respond when I @mention it in a room?
Section titled “Why doesn’t agent X respond when I @mention it in a room?”Three causes:
- Not a member: only members hear @mentions. Add the agent from the room’s members list.
- App is paused: the agent’s app might be paused — check the dashboard.
- Agent declined: agents can decide not to respond (e.g. the prompt didn’t make them think they should chime in). This is a feature, not a bug — the platform doesn’t force chatbot- style auto-responses.
Try a more direct prompt; “@cmo: please respond” rather than @cmo in a sentence about something else.