Choose an integration

Use an Anectico SDK when you want customer identity, errors, and application telemetry to connect automatically. Use OpenTelemetry when you already have instrumentation and want to send it to Anectico without replacing it.

Application SDKs

Application	Start here	Best for
Browser, Node.js, React	JavaScript / TypeScript	Browser and backend telemetry, errors, replay, identity
Django, Flask, FastAPI, Celery	Python	Framework requests, logs, errors, identity
Go services	Go	Metrics, traces, logs, errors, identity, gRPC and HTTP services
iOS, Android, React Native, Flutter	Mobile	Native crashes, identity, sessions, events, remote flags, headless surveys and optional structural replay

Compare capabilities

The mobile SDKs intentionally have a smaller surface than the server SDKs. “Propagation” means the SDK can attach trace and customer context to a trusted backend request; it does not record full mobile request traces by itself. All four mobile SDKs also expose startAgentRun for explicit invoke_agent spans; this is not general-purpose or automatic network tracing. Android's captureLog writes OTLP logs; captureMessage on mobile records an error or message event, not a standalone log. See the mobile SDK references.

Integration	Traces	Metrics	Logs	Errors	Identity and events	Replay
JavaScript / TypeScript	Yes	Yes	Yes	Yes	Yes	Browser only
Python	Yes	Yes	Yes	Yes	Yes	No
Go	Yes	Yes	Yes	Yes	Yes	No
iOS	Propagation and agent-run spans	No	No; messages are error events	Caught and native crashes	Yes	Optional UIKit structure
Android	Propagation and agent-run spans	No	Durable captureLog	Caught and native crashes	Yes	Optional Android View structure
React Native and Flutter	Propagation and agent-run spans	No	No; messages are error events	JavaScript and Dart errors, plus native crashes	Yes	Optional structural adapters
Existing OpenTelemetry	Yes	Yes	Yes	As emitted telemetry	Manual attributes	No

Provider-specific AI wrappers are available in JavaScript, Python, and Go. Browser replay is a separate JavaScript import and permission; it is never enabled by installing the base package.

Mobile flags, surveys and replay

All four mobile SDKs expose remote flags and headless surveys. Your application renders the survey UI. Delivery keys are separate from telemetry and capture keys; follow the platform guide for setup and inspect stored evidence separately from an acknowledgement.

Native structural replay is optional on iOS, Android, React Native and Flutter. It records bounded structure and declared actions rather than screenshots. Use the source coverage and independent consent controls in each platform guide; an SDK implementation or an accepted upload does not establish physical-device qualification.

The Android SDK supports minSdk 24 without java.time desugaring in your application. The Android time-value contract also applies to the native Android SDK bundled with React Native and Flutter.

Check the plan before rollout

Read billing and plan allowances and agent budgets before expanding collection or connecting more agents. Use the checked current allowance read; missing headroom is unknown. Event admission, retention and replay limits are defined in Plans and limits.

Install during early access

Anectico is in early access and the public npm, PyPI, Maven, and pub.dev packages are not published yet. Use the package artifact, repository access, or exact install coordinate supplied during onboarding. The Go and iOS SDKs can be installed from an authorized Anectico repository checkout. Do not guess a registry version from the package name; the language guides label registry commands as post-release instructions.

Have your agent integrate it

For feature flags and product events, your own agent can do the integration in your repository: it inspects the code, shows you a plan, writes the integration, runs your application as synthetic people and asks Anectico whether the exact samples arrived. Today that covers a Node.js server with the JavaScript SDK and any server over HTTP without an SDK. Errors, traces, logs, replay, surveys, product experiments, browser and mobile applications are not covered by that workflow yet. See Ask your agent to integrate Anectico.

Existing OpenTelemetry setup

Keep your current OpenTelemetry libraries and point their OTLP exporter at Anectico. This is the lowest-change path for traces, logs, and metrics.

OpenTelemetry alone does not automatically create Anectico's cross-signal customer identity. Add the anectico.distinct_id attribute or W3C baggage at your trusted application boundary if you want telemetry to appear on customer timelines.

Configure OpenTelemetry

For custom counters, gauges, and histograms, see Record application metrics.

Choose the first application carefully

Start with one customer-facing journey, not every service. Good first choices are checkout, onboarding, search, or the main AI workflow. The first integration should be able to produce:

• a stable customer ID;
• at least one request trace;
• a captured error; and
• browser replay when the journey has a web interface.

That is enough to validate the complete investigation workflow before rolling Anectico out further.

What not to install

You do not need an Anectico backend, local database, or sidecar. Anectico's SDKs send data to the managed ingestion endpoint. An OpenTelemetry Collector is optional and useful only when it already fits your deployment.