Having our own domain is more than just a new URL. It's a step towards making LogsCord a long-term platform with its own ecosystem, documentation, APIs and developer tooling.

All pages from the previous domain are automatically redirected, so existing links will continue to work.

💬 Official Discord server

We've also launched our official Discord community:

https://discord.gg/hpqqU9NUyh

This server isn't only for support.

It will become the central place for:

Feature announcements
Beta releases
Community discussions
Bug reports
API discussions
Developer support
Open source contributions

Whether you're simply using LogsCord or building Discord applications yourself, you're welcome.

👨‍💻 LogsCord is becoming a platform for developers

Until now, LogsCord has mainly focused on helping communities observe and understand what happens inside their Discord servers.

Our next objective is much bigger.

We want developers to be able to build applications and bots that integrate directly with the LogsCord ecosystem.

Soon, your applications will be able to send their own logs to LogsCord alongside native Discord events, allowing you to correlate everything from a single interface.

Instead of only answering questions like:

Who deleted this channel?

You'll also be able to answer:

Which bot handled this interaction?

Which service produced this exception?

Which command triggered this API request?

Which shard was responsible?

LogsCord aims to provide observability for the entire Discord application stack.

📦 Official npm organization

We're also introducing our official npm organization:

https://www.npmjs.com/org/logscord

Packages published under @logscord will provide reusable building blocks for Discord applications.

The first public package is already available:

@logscord/authorizer

https://www.npmjs.com/package/@logscord/authorizer

It provides a centralized authorization engine allowing multiple bots and services to share the exact same permission policies instead of duplicating permission logic everywhere.

🔍 Logging SDK coming soon

Very soon we'll also release a dedicated logging package under the @logscord scope.

(Suggested package name: @logscord/logger* — simple, immediately understandable and consistent with the ecosystem.)*

Rather than being tightly coupled to LogsCord, this SDK is being designed around strategies.

You'll be able to define one or more log collectors and choose where logs are sent.

For example:

LogsCord
SQLite
PostgreSQL
Files
Custom collectors
Multiple destinations simultaneously

This means you won't be locked into a single backend.

Sending logs to LogsCord will simply become one strategy among many, making it easy to add redundancy or integrate with your existing infrastructure.

🌍 Open source

A public GitHub organization is also on its way.

Several open source projects will be published over the coming weeks, including packages, SDKs and components used internally by LogsCord.

Our goal is to make it easier for developers to build reliable Discord applications while sharing the tooling that powers LogsCord itself.

Our vision

LogsCord continues to evolve.

Our ambition is no longer to be "just another logging bot."

We want LogsCord to become the observability standard for serious Discord applications and communities.

A platform where Discord events, application logs, permissions, analytics, moderation and AI-powered insights all come together in one place.

This is only the beginning. 🚀