Best for a specific problem: an ingest request that will not land, a console screen that disagrees with what you expected, or a question about your account, organization, or plan allowance.
Support
Get help from the person who builds Errorcore.
Errorcore is built and operated by one engineer. Email arrives in a mailbox that is read personally, and the booking button below opens a calendar that books time directly: no queue, no qualification call before you get an answer.
Two ways to reach me
Write when something is wrong. Book when something needs a conversation.
Book a call
Best for onboarding, for deciding whether Errorcore fits your stack, or for walking through your pipeline together. 30 minutes over video, nothing to prepare.
Book a call
Pick a 30-minute slot.
The button opens the calendar in a dialog over this page. Choose any open time. Google sends the invitation and the video link. If you have a real production failure you are able to talk about, bring it: that is the quickest way to find out whether the evidence Errorcore captures is the evidence you actually need.
The button and the booking grid are both served by Google Calendar, so this page loads Google’s button script and the dialog loads the grid itself: each request shares your IP address and any Google cookies you already hold with Google. If your browser blocks either one, or you would rather not open the dialog, open the booking page on Google or email [email protected] and we will agree on a time by hand.
Writing a request
Send enough to diagnose, and nothing that puts your users at risk.
Details that let me answer on the first reply.
- The affected page or documentation path.
- Approximate time and time zone.
- Browser or SDK version.
- The visible status or safe error category the product showed you.
- Reproduction steps against synthetic data.
Redact identifiers before you send.
Organization, project, case, event, trace, and object identifiers point at a tenant. Describe their shape instead of pasting them, unless a reply from support asks for a specific safe substitute.
Never send secrets or customer evidence.
Passwords, API or MCP keys, encryption keys, cookies, authorization headers, customer payloads, decrypted runtime values, personal data, database contents, private keys, billing credentials, and production screenshots that expose customer evidence do not belong in an email. Support will never ask you for any of them.
Coverage
What support handles.
- Account and organization access.
- Setup, SDK configuration, and a controlled test event.
- Ingestion, processing, retention settings, and console behavior.
- Plan allowances and billing questions.
- Privacy and data-handling questions.
Limits
What the beta does not promise.
No response-time commitment.
The mailbox is monitored and every message is read personally. The public beta names no response time, no support SLA, and no refund policy.
Security reports need a private channel first.
A verified private vulnerability-reporting route is not published yet. Do not put a suspected vulnerability in a public issue or in a first email. Write to [email protected] asking for a private channel, and one will be opened before you send any detail.
Paid checkout is disabled.
Plan allowances are enforced, but no paid plan can be purchased during the beta. Billing questions are welcome; billing changes are not yet possible.
Before writing, the troubleshooting guide covers the common setup and ingest failures, the security page states what the system verifiably does with your data, and the privacy document describes the intended data handling.