DOCUMENTATION

Docs

How to send data to a codesafe instance, and how to build your own client.

Three ways in. All of them are the same HTTP call underneath.

Which one do I need?

  • Running WordPress? Install the plugin, paste a key, done — nothing else on this page applies.
  • Running PHP or Node? Use the drop-in client, or write the twenty lines yourself.
  • Already instrumented with OpenTelemetry? Point the collector's logs pipeline at codesafe.
  • Anything else — Python, Go, Java, Rust, .NET? One POST, a key in a header, JSON in the body.
  • A CMS with no client yet — TYPO3, Drupal, Shopware, something in-house? Write to us. We build the client and integrate it; you do not pay for the plumbing.

The rules every client follows

  • Fire and forget. Reporting may never slow or break the app that reports.
  • One second, hard. A codesafe instance that is down costs your users nothing.
  • Never retry what may have arrived. Only an unopened connection or a 429/503 goes once more, off the request path.
  • Redact first. Passwords, tokens and cookies never leave the box.
  • Batch, then flush. PHP sends once after the response; a long-running process every second or two.

There is no SDK you must use and no vendor lock to accept. The WordPress client is public and is a working reference implementation of everything on these pages.