SDK OBSERVABILITY FOR EVERY APP

Know what broke.
Find the next step.

Collect errors across browser, mobile, and server. Trace events, group related issues, and see what needs attention.

Read the docs Console

WEB FLUTTER NODE

OVERVIEW

Everything in view

Last 24 hours · all apps

Live

Events1,284Across 3 apps

Errors38Needs review

Open issues02Grouped by cause

Event activityLast 24 hours

00:0006:0012:0018:00Now

Product preview · sample data

BUILT FOR TEAMSOne protocolEvent receiptsApp accessVerified archives

THE PRODUCT

From event to
resolution.

Capture reliably. Investigate with context. Keep access and retention under control.

01COLLECT

Collect anywhere

Browser, Flutter, and Node share one protocol. Event receipts and stable IDs make retries reliable.

Event receiptsSafe retries

02INVESTIGATE

Investigate faster

Filter events by app, environment, time, or level. Follow traces and track related errors as issues.

Event searchIssue groups

03CONTROL

Control access

Give members access only to their apps. Public App Keys can send events but cannot read logs.

App rolesAudit log

04RETAIN

Archive with proof

Verify archives before deleting hot data. Older events stay searchable in cold storage.

7-day searchCold archive

GET STARTED

Get to your first event.

Create an app, issue a key, and connect the SDK.

Integration guide

Create an app

Add a Web, mobile, or server app and set access.

Get a key

Use a public App Key in clients and a private key on servers.

Connect the SDK

Send an event, then find it in Live, Events, or Issues.

FOR DEVELOPERS

One flow.
Every runtime.

Capture browser errors, fetch activity, and offline events. Node and Flutter use the same delivery protocol and event receipts.

Explore all SDKs

browser.tsSDK / WEB

import { createBrowserMaxLogs } from '@maxlogs/sdk/browser'

const logs = createBrowserMaxLogs({
  endpoint: 'https://ingest.example.com/v2/events/batch',
  credential: 'mlpk_…',
  appId: 'your-web-app',
  env: 'production',
  platform: 'web', runtime: 'browser', source: 'browser',
})

logs.captureError(new Error('Checkout failed'))

COMMON QUESTIONS

Answers before you start.

A quick guide to integration, access, and error investigation.

Explore the SDK docs

What is MaxLogs?

MaxLogs is an SDK log and error monitoring platform. It collects events from your apps, makes them searchable, and groups related errors into issues your team can investigate.

Which apps can send events?

The SDK documentation covers browser apps, Node and SSR services, Flutter apps, and uni-app mini-programs. Web and a mini-program can share one App ID and public key; events remain labeled by platform. Use separate apps when you need independent access.

Can an App Key read my logs?

No. A public App Key can send events only. Reading logs requires a console session and permission for the specific app.

How are repeated errors handled?

Related error events are grouped into issues. You can inspect evidence, follow the activity timeline, and track each issue through its resolution.

What happens when a device is offline?

Supported client SDKs keep a bounded local queue and retry with the same event ID. The ingest API returns a receipt for each event, so the SDK can distinguish accepted events from rejected ones.

How do I create an account?

Create an account to start a private workspace where you are the administrator, or accept an invitation to join an existing workspace with its assigned app access.

READY TO EXPLORE?

Ready to try MaxLogs?

Create an app, send an event, and trace it in the console.

Console Try the demo

Know what broke.Find the next step.