Help Centre

Last updated: August 25, 2026

Getting started

Timelinefix.AI is a stateless tool that turns raw incident notes into a structured timeline. There are no accounts, no dashboards, and no setup.

  1. 01

    Open the tool — go to the App page. You will see a text area and an "Analyze timeline" button.

  2. 02

    Paste your notes — copy raw material from your incident channel: chat excerpts, log entries, timestamps, actions taken, observations. Any plain text works. Click "Load sample notes" to see the expected format.

  3. 03

    Click "Analyze timeline" — the tool processes your text and returns a structured timeline, summary, gap analysis, root causes, and action items. Results appear below the input area.

  4. 04

    Review and copy — the timeline is displayed in your browser. It is not saved anywhere server-side. Copy the output before leaving the page; refreshing clears the results.

Demo mode? If the tool shows a yellow "Demo mode" banner, the LLM API key is not configured. The page still loads sample data so you can see the interface, but real analysis requires the operator to set LLM_API_KEY. See the "Known limitations" section below.

Frequently asked questions

Is my data stored or saved when I use the tool?
No. The tool is stateless. Your text is sent from your browser to the Cloudflare Worker, which forwards it to the LLM API for processing, and the result is returned to your browser. Nothing is stored server-side. Refreshing the page discards your input and results. The Privacy Policy has full details.
How accurate is the timeline? Can I rely on it for a postmortem?
The timeline is generated by a large language model based on the text you provide. The quality of the output depends directly on the quality of your input. Gaps in the source material produce gaps in the timeline — the tool marks these explicitly rather than inventing connections. Always review and edit the generated timeline before filing a postmortem. The tool is an aid, not an authoritative record. See the Terms of Service for the full disclaimer.
What counts as a "gap" in the timeline?
A gap is any period in the incident where the source material contains no information about what happened. For example: logs stop for 45 minutes with no explanation, or chat messages jump from 09:28 to 10:45 without covering what was tried in between. The tool highlights these gaps with an amber marker. Showing gaps is deliberate — a timeline that hides uncertainty is worse than one that names it.
Can I export or share my timeline?
Not yet. The tool displays results in the browser and does not provide a download or share function. If you need to save a timeline, copy the text from the page manually. Export (JSON and Markdown) is under consideration but not scheduled.
Does the tool connect to my monitoring system (PagerDuty, Datadog, Grafana, etc.)?
No. The tool reads only the text you paste. It does not connect to any monitoring, alerting, or paging system. If you want to create a timeline from an incident, you will need to gather the relevant chat logs, alert messages, and notes yourself and paste them in.
Why does the tool show "Demo mode"? How do I make real analysis work?
The tool requires an LLM API key (LLM_API_KEY) to be configured server-side to perform real analysis. If this key has not been set, the tool falls back to displaying sample data so you can see the user interface. The operator needs to set this environment variable on the Cloudflare Worker for real analysis to function. This is not something users can fix from their end.

Known limitations

These are honest descriptions of what the product does not do yet or cannot do by design. None are promised for a future date unless explicitly stated.

LLM API key required Not configured
The tool currently runs in demo mode because the server-side LLM_API_KEY has not been set. Real analysis will work once the operator configures this key on the Cloudflare Worker. Until then, the interface displays sample data as a preview.
No user accounts or saved data
Every session is stateless. There is no database. If you refresh the page, your input and results are gone. There is no way to log in, bookmark a timeline, or retrieve a past analysis. This is by design — the tool does not hold onto your incident data.
No email, alerts, or notifications
The product cannot send email, push notifications, or scheduled digests. Results are displayed in the browser only. There is no "email me this timeline" feature.
No team collaboration or sharing
There are no shared workspaces, team accounts, or timeline links. Each person uses the tool independently in their own browser. There is no way to share a timeline with a colleague through the tool itself.
No timeline export (JSON, Markdown, PDF)
The timeline is displayed on screen only. There is no export button. If you need a copy, select and copy the text manually. JSON export is under consideration but has no delivery date.
No payment processor connected
The Pro plan checkout on the Pricing page is a UI demonstration only. No real payments can be taken. The pricing page clearly labels this.
No legal entity registered
The product is operated without a registered company. There is no jurisdiction, registered address, or named legal entity. The Terms of Service and Privacy Policy state this and will be updated when the entity is established.

Contact us

Email support

No support email address is available yet.

The operator has not set up a mailbox or ticketing system for this service. This page will be updated with a contact address once one exists.

Billing and legal inquiries

Not available.

No billing email, legal address, or company contact has been established. Inquiries about payments, data protection, or legal matters cannot be directed to any destination at this time. The operator will provide contact details when the business entity is registered.

What to do if you need help now: The most common questions are answered on this page. If your issue is not covered, please review the Privacy Policy and Terms of Service for context about how the product works. If you are encountering a technical issue (the tool does not load, returns errors, behaves unexpectedly), record the exact steps and what you see — this information will be needed when the operator establishes a support channel.