How ShipTale works
ShipTale connects read-only provider data, normalizes it into a common timeline, and marks successful Vercel or GitHub production events as releases. It associates Sentry and supported Stripe events using stored evidence and schedules aggregate PostHog measurements, then presents each release as a Tale with confidence labels and source links.
A Tale is the release-centered view in ShipTale. It begins with a production release and follows the operational and customer signals that ShipTale can defensibly associate, while standalone events remain available in the wider timeline.
A readable narrative is useful only when its limits are visible. ShipTale stores the method, confidence, algorithm version, and correlation time so an association can be explained and reconciled as provider history arrives.
| Area | Supports | Does not claim or do |
|---|---|---|
| Import | Selected provider projects and supported event fields | An unrestricted copy of provider data |
| Normalization | One provider-neutral event model | Discarding provider identity |
| Presentation | Chronology, evidence, and source links | Replacing provider consoles |
Add read-capable credentials and choose the provider projects to monitor.
Import events, mark releases, deduplicate records, and evaluate correlation evidence.
Use the Tale as a starting point, then follow source links for native detail.
Free tool
Generate a practical release checklist tailored to your deployment type, stack, and risk areas.
Apply Tales after every release.
See how releases are marked.
Review data and credential boundaries.
Connect Vercel, GitHub, Sentry, PostHog, and Stripe for free. Choose Pro or Pro Lifetime for more project capacity and history.