kromise
Sentry SDK compatible · AWS Tokyo region

One line changes. One line The DSN.

Keep the official Sentry SDK exactly as it is. Your events are stored and processed in AWS ap-northeast-1.

⚠ This is still in development. Commercial availability, pricing and SLA are not decided yet.

instrument.tsCopy
// before
Sentry.init({ dsn: "https://<key>@o0.ingest.sentry.io/1234567" });

// after — only the destination changes
Sentry.init({ dsn: "https://<key>@ingest.kromise.com/1" });
One line · SDK unmodifiedSame step for the official SDKs of the major languages

LIVE DEMO

Press it and watch it arrive.

On the public demo, pressing the button makes Sentry's own unmodified SDK send an exception. Seconds later it appears in the list below.

Send an error from the demo
Unresolved errors4

Error: user <email> not found

app/checkout/page.tsx · handleSubmit

production3 min ago12
at handleSubmit (app/checkout/page.tsx:42:11)
at onClick (components/Button.tsx:18:5)
at HTMLUnknownElement.callCallback (react-dom.js:4164:14)
at Sentry.captureException (@sentry/browser 10.75.0 · unmodified)

TypeError: undefined is not a function

src/hooks/useCart.ts · recalculate

web-frontend6 min ago48

ValueError: invalid literal for int() with base 10: 'null'

worker/tasks/import.py · parse_row

api-worker14 min ago5

Error: Request timeout after 30000ms

lib/http/client.ts · withTimeout

checkout27 min ago31

The list above reproduces the public demo's screen.

Features

01

Works with the official SDKs

Verified against the official SDKs of the major languages. There is no proprietary SDK and no fork to adopt.

02

Stored and processed in Tokyo

Events are stored and processed in AWS ap-northeast-1. They are received by a CDN at the nearest edge location and forwarded to Tokyo.

03

Leaving is one line too

Put the DSN back and the next event returns to where it came from. Arriving and leaving cost the same.

Questions

Do you use Sentry's code?

No. This is an independent implementation. What it matches is the published wire protocol.

Who can read the errors I send to the demo?

The demo is apublic project, so anything you send is readable by anyone. It also carries whatever browser detail the official SDK attaches, so please use it for trials only. For security and abuse prevention we keep access logs (IP address, user agent and requested URL) for 30 days and then delete them. They are not used for anything else.

Can I use it today?

Not commercially — that has not started. If you would like to try it, or talk through your requirements, write to kromise@jugoya.ai.