Fully Managed Logwell
as a Service

Deploy Logwell as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Logwell is a self-hosted log platform: live streaming, full-text search across structured events, and OTLP-compatible ingestion: combining the convenience of a metered logging service with the control of software you own.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

Logwell

Logwell

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Logwell Preview Image

ABOUT THE SOFTWARE

What is Logwell

Logwell collects application logs from your services, stores them as structured rows, and gives you one screen to stream and search them. It handles logs only. Metrics and distributed traces stay with whatever tool you already use for those.

Logwell is released under the MIT licence and is maintained on GitHub by Divanshu Chauhan. The stack is deliberately small: a SvelteKit front end, the Bun runtime, and PostgreSQL as the only datastore. Full-text search runs on a PostgreSQL tsvector column with a GIN index, so there is no Elasticsearch cluster to size, shard or restart. Live tailing uses Server-Sent Events fed by an in-memory bus rather than database polling.

Ingestion is OTLP-compatible, so services already exporting OpenTelemetry logs can point at Logwell without a rewrite. First-party SDKs are published for JavaScript, Python, Go and JSR, and anything that can send an HTTP request with a project API key will work. The project is young and its maintainer describes it as alpha software: single-user sign-in, no role separation, and breaking changes between versions are all documented facts rather than surprises.

FEATURES

What Logwell does

Logwell is built around four jobs: take logs in from anything, keep them in PostgreSQL, show them live, and let you search them later. Everything below is a capability of the software itself rather than of the platform running it.

Live log streaming

Server-Sent Events push new lines to the browser as they arrive, fed by an in-memory bus instead of a database poll loop.

Full-text search

Search runs on a PostgreSQL tsvector column with a GIN index, so queries stay fast without a separate search engine.

OTLP-compatible ingestion

Services already exporting OpenTelemetry logs can send to Logwell by changing an endpoint rather than a library.

Per-project API keys

Each project gets its own write key, so one instance can hold several applications without mixing their streams.

Structured log storage

Logs land as rows with level, timestamp, message and metadata, which is what makes filtering and search meaningful.

Incident detection

Repeated error patterns are grouped into incidents and closed automatically once the pattern stops for a set interval.

Export to CSV or JSON

A project export endpoint returns log rows in either format for archiving or for loading into another tool.

First-party SDKs

Client libraries are published for JavaScript, Python, Go and JSR, alongside plain HTTP ingestion for everything else.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to Logwell the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Logwell

Metered logging services bill on two axes at once: volume ingested and events indexed, with the index price rising as the retention window lengthens. Teams move to Logwell to make that bill a flat line. Managed Logwell removes the operational tail that usually comes with the move.

Running Logwell yourself is more than a container. Someone has to keep PostgreSQL patched and backed up, renew certificates, watch the ingestion endpoint, and read the release notes before every upgrade on a project that has not tagged a stable release. That work does not scale down when the log volume is small.

The failure mode specific to Logwell is disk. Its maintainer says so openly: there is no protection against a runaway logging loop filling the volume. The retention setting accepts a value meaning never delete, and the per-key ingest limit defaults to 600 requests a minute, which is generous enough that a misbehaving service can write for days before anyone looks. A log platform that dies with a full disk takes the evidence of why it died with it.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Logwell on DANIAN

The teams below are the shapes that recur: one person carrying several services, a small product team that wants search without an operations hire, and an agency keeping client logs apart. Configuration differs mostly in retention and in how many project keys are issued.

AUTOMATION OPERATOR

Two bots and a scraper, one place to look

One operator runs a chat bot with a large user base plus a scraping service. Each gets its own project key, so a crash in the scraper never buries the bot's stream. Retention stays at 30 days and the database holds a few hundred thousand rows without complaint.

FOUR-PERSON SAAS TEAM

Dropping the metered bill without hiring an operator

An API product exporting OpenTelemetry logs changed one endpoint and kept its instrumentation. Retention went to 90 days for incident review. The team searches by request identifier during on-call and has no search cluster to maintain.

TWO-PERSON AGENCY

Client logs kept apart, and handed over at the end

Six client applications, six project keys, one instance in the region the largest client asked for. At the end of each engagement the agency exports that project to JSON, hands it over, and revokes the key without touching the others.

COMPARISON

Four ways to run Logwell

Logging vendors price by volume, not by seat, so the table below compares monthly log volume rather than users. That is the axis on which a metered bill actually moves. The DANIAN row is flat because the price does not respond to either axis.

Path1 GB / month10 GB / month100 GB / monthWhat you also carry
Metered logging service (SolarWinds Papertrail)$5/mo$50/mo$500/moSeven days of searchable retention on standard plans. Older data goes to object storage and stops being searchable in the product.
Self-host on a production-class VPS€24/mo€24/mo€24/mo + storagePatching, certificate renewal, PostgreSQL backups, disk watching and upgrade reading. Roughly a few hours a month, more when something breaks.
Home server (Intel N100 mini PC)~€180 once~€180 once~€180 once + disksElectricity, your own uplink, no off-site backup copy, and no answer when the disk fails while you are away.
DANIAN managed Logwell€9/mo€9/mo€9/moRetention tuning, ingest limiting, backups, certificates and monitoring are ours. You choose the region and the retention window.

Each app includes 30 GB of storage and 1,000 GB of traffic. At high ingest volumes we tune retention to fit that allowance, or add storage with your consent first. Third-party prices are list prices at the time of writing and are shown for orientation, not as a quote.

BY INDUSTRY

Logwell for specific industries

Log retention is where sector rules bite. The four below each set a different retention window and a different expectation about what gets written into a log body. Both are configuration choices, so we make them before handover rather than after a request.

Agencies work against the OWASP Application Security Verification Standard, whose V7 section on logging and error handling asks that security-relevant events be recorded and that credentials and payment details never reach a log body. On DANIAN we issue one project key per client application, so a key can be revoked at the end of an engagement without touching the others. A typical workflow: an agency carrying six client applications searches one client's stream during a handover call, exports that project to JSON, and rotates its key the same day. Retention is set to the engagement term rather than the 30-day default, which for most retainer work means 90 days.


NIST Special Publication 800-92, the guide to computer security log management, asks organisations to define a retention period and collect logs centrally rather than leaving them on each host. On DANIAN the retention window is the setting we confirm at signup, raised from the 30-day default when incident review needs a longer look back. A typical workflow: a product team exporting OpenTelemetry logs repoints its collector at the Logwell ingestion endpoint, keeps its existing instrumentation, and searches by request identifier during on-call. Ninety days is the window most teams settle on, and it is set once rather than renegotiated.


Providers inside the scope of the NIS2 Directive work to Article 23, which expects an early warning within 24 hours of becoming aware of a significant incident and a fuller notification within 72 hours. Reconstructing a timeline that fast needs searchable logs that outlive the incident. On DANIAN we keep the incident auto-resolve interval at its default so short-lived error bursts close themselves and only sustained patterns stay open. A typical workflow: an operator searches the affected customer's project by timestamp range, exports the matching rows, and attaches them to the 72-hour notification.


Section 802 of the Sarbanes-Oxley Act requires records supporting financial reporting to be retained for seven years. Logwell is not that system of record, holding no tamper protection and signing in one user, but engineering teams often want their developer-facing view to reach back as far as the record itself. On DANIAN that means setting retention to 2,555 days and sizing storage to match before the first write, rather than discovering the ceiling later. A typical workflow: an engineer traces a settlement job from three years ago by searching the job identifier, and exports the matching rows for the finance team.


FAQ

Frequently asked questions

Three groups below. The first covers how Logwell behaves and what we change from a plain install. The second covers moving in and moving out. The third covers billing, support and the platform, and reads the same on every app page because those answers are platform-wide.

01

Technical and configuration

PostgreSQL, and only PostgreSQL. Logs are stored as rows and full-text search runs on a tsvector column with a GIN index. There is no Elasticsearch or OpenSearch cluster in the picture, which is the main reason the memory footprint stays small.
New lines are pushed to the browser over Server-Sent Events, fed by an in-memory bus rather than a polling query. The stream flushes on a short batching window, so a busy service does not open a socket write per line.
Yes. Ingestion is OTLP-compatible, so a service already exporting OpenTelemetry logs changes an endpoint rather than a library. First-party SDKs are also published for JavaScript, Python, Go and JSR, and plain HTTP with a project key works for everything else.
No. Sign-in is single-user and there is no role separation. If your team needs per-person accounts on the log tool itself, Logwell is the wrong choice today and we would rather say so before you migrate than after.
Not with a project key. Project keys are for writing logs in. Reading happens in the interface, or through the export endpoint, which returns a project's rows as CSV or JSON up to a per-call row limit.
It detects incidents and groups repeated errors, but it does not push them anywhere. There is no webhook or email alerting in the software. We monitor the instance itself, so a Logwell that stops accepting writes still pages an operator.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
There is no bulk importer. The usual approach is to point your shippers at the new endpoint, keep the old system read-only until its retention window expires, and export anything you need to keep from the old tool while you still can.
One endpoint and one key, in most cases. Install a first-party SDK or send a signed HTTP request with your project key. Services already emitting OpenTelemetry logs usually need only a collector endpoint change.
Yes. Point a subdomain at the instance and we issue and renew the certificate for it. The application's origin setting is configured to match, which matters because sign-in breaks quietly when it does not.
Yes. The export endpoint returns a project's rows as CSV or JSON, and because everything lives in PostgreSQL we will also hand you a database dump on request. There is no format in the middle that only we can read.
Yes, on every app. Send us the records you can already see and we will tell you exactly what to change. If you would rather we did it, delegate the subdomain and we will handle it.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Logwell for 7 days

No card. Cancel from the dashboard.