We don't leave after launch
Amicon keeps watching your project: HTTP availability checks, app errors via our SDK, release-aware analytics and alerts to the mobile app. All in one dashboard, no third-party vendors.
99.9%
availability target
30 days
error history retention
5 min
minimum check interval
real-time
5–60s alert delivery
A full observability loop
Six things we do so that you're the first to know about issues with your product.
Uptime monitoring
Regular HTTP checks for every URL. Configurable interval: 5, 15, 30, 60 minutes, 6 hours, 1 day.
SDK error collection
JS exceptions, React Native crashes, server-side fatal errors. Fingerprint dedup, 30-day retention.
Auto-discovery
We parse `<link rel="alternate" hreflang>` on the main page and add every language variant as a separate endpoint.
Anti-spam alerts
First event is an immediate push, then silence until resolved. Email digest at most once a day.
Mobile dashboard
Monitoring tab inside the Amicon app: statuses, errors, manual rechecks and per-channel alert settings.
Transparent control
The client sees their projects; the Amicon team provides support. Turn off per-site notifications with a single tap.
Less than an hour from setup to first alert
We register the site
We create the project in the Amicon admin, add URLs and a check interval. Hreflang variants are picked up automatically.
Issue an ingest token
An ingest token is issued from the admin. It is shown only once — we store hashes so leaking the database doesn't leak the token.
Install the SDK
One line: `initMonitoring({ apiKey, siteId })` in your RN/web app. The SDK collects and ships errors in the background.
You see everything in the dashboard
Statuses, history, error charts, push to the Amicon mobile app. Metrics refresh every 30–60 seconds.
One line in your code
Lightweight `@amicon/monitor-rn` and `@amicon/monitor-web` packages plug in in five minutes. Non-blocking, no PII leaks, offline queue.
- React Native: JS crashes and native exceptions via a @sentry/react-native-compatible format
- Web: window.onerror, unhandled rejections, fetch-interception for server 5xx
- Offline queue and batching — we ship what's accumulated once the network is back
- PII sanitization: masks for phones/emails/tokens in stack traces before sending
1import { initMonitoring } from '@amicon/monitor-rn'; 2 3initMonitoring({ 4 apiKey: 'mon_••••••••••••••••', 5 siteId: 'site_••••', 6 release: '1.4.2', 7 environment: 'production', 8});Frequently asked
How long is the error history kept?
30 days. Enough to find regressions between releases without paying for forever-storage like the big observability vendors.
Where does the data go?
To our server in Russia. We don't share with third-party vendors, we don't send data to other countries. Token hashes in the database — the raw token is only visible at the moment of issuance.
Our site has 8 languages. Do we pay per language?
No. One project = one monitored site. Language URLs are endpoints inside the site and are covered by a single price.
How much does it cost?
For projects we deliver turnkey, basic monitoring is included in support. Advanced settings (5-minute interval, custom alerts) are negotiable — drop us a line.
Let's monitor your project
Tell us briefly what you already have — within a day we'll propose an SDK integration plan and a check schedule.