livecord.net

What It Is

Livecord is a hosted selfbot/relay service whose core goal is to keep user accounts continuously online and mirror channel content that the user can read into a private workspace they control in real time. It does not require installing a browser extension, desktop client, or local agent; instead, it runs the session in the cloud and lets users manage presence, mirrors, message streams, and health status through a Dashboard.

Core Features

Functionally, Livecord is divided into three parts: Presence, Mirrors, and Always-on relay. Presence supports custom status, rich activity, Spotify-like listening status, and rotation based on time or trigger conditions. Mirrors can forward source channels to a webhook or HTTPS sink, and claims to sync edits, deletes, threads, attachments, embeds, and reactions, with latency potentially under 1 second. Its filtering pipeline includes regex, user allow/block lists, role-based access gates, and embedding-based topic matching. The relay runs on multi-region infrastructure and includes automatic failover, gateway pinning, reconnection, and rate-limit backpressure handling.

Pricing and Deployment

Pricing is currently extremely aggressive: all features are free, no credit card is required, there is no trial countdown, and it includes unlimited sessions, unlimited mirrors, the full presence engine, filtering pipelines, and 30-day message retention. That said, the copy also describes this as “while we're building/forever for now,” so the long-term business model remains uncertain. In terms of deployment, it is a fully hosted service; no self-hosting option is visible, and there is no stated open-source information.

Pros and Cons

The advantages are its short onboarding path — four steps from session token to live feed — relatively complete mirroring granularity with support for edits, deletes, threads, and attachments, and webhook/HTTPS sink support that makes it easy to plug into existing user workflows. The downsides are also obvious: it relies on session tokens and a selfbot model, and the FAQ explicitly reminds users that they are responsible for compliance with the policies of the services they connect to. The service retains mirrored messages on its servers for 30 days, so sensitive-information scenarios require caution. There is also limited disclosure about the company entity, country, open-source status, API/SDK documentation, and security details.

Who It’s For and Access from China

It is suitable for individuals and small teams that need always-on presence, aggregated community announcements, trading signals, whitelist alerts, or on-chain notifications. It also fits information-flow scenarios where multiple channels are consolidated into a private workspace. It is not suitable for enterprises with strict requirements around platform compliance, auditing, self-hosting, and data sovereignty. Access from mainland China is not covered in the available text, and there is little information about network connectivity, payment methods, or alternatives. While no payment is currently required, users should still test access stability for themselves in real-world use.