Recent & live runtime logs
Review available past-hour Vercel, Netlify, and Render runtime history, then follow new output as providers send it.
DESKTOP LOGS, WITHOUT THE NOISE
Catch up on recent Vercel, Netlify, and Render runtime logs, follow new output, and check application health from your desktop. With a small cat keeping you company.
A QUIETER WAY TO KEEP UP
One small desktop workspace for runtime output, deployment context, and public endpoint checks — without sending logs through another hosted service.
Review available past-hour Vercel, Netlify, and Render runtime history, then follow new output as providers send it.
See deployment status and recent Vercel and Render build logs. Netlify build logs stay in its dashboard.
Check a public HTTPS endpoint every 15 seconds. Health checks don't collect application logs.
Edit project names, descriptions, colors, and tags. Scope connected applications to their environments.
Search messages, filter sources and severity, and find HTTP methods without case sensitivity.
Restore the newest 1,000 entries across projects, copy filtered text, or export JSON for longer-term records.
Reuse a saved token across applications on the same provider. Credentials stay out of the renderer.
Get alerts while Simply Logs is open with a window, with a pixel cat keeping quiet company.
HONEST ABOUT THE EDGES
Simply Logs reads directly from provider APIs and streams. Retention, permissions, query limits, and deployment selection still shape what you can see.
More answers in the FAQProduction follows its active deployment, including promotions and rollbacks. Preview follows the latest ready preview deployment.
Production follows the published deployment; preview follows the latest ready deploy preview or branch deploy. Build logs stay in Netlify.
Logs are scoped to the selected service. Build history uses a time range from the latest deploy's creation and can include nearby deploys.
Live entries arrive as providers send them. Deployment selection refreshes roughly every 30 seconds; failed history or streams warn and retry. Reconnection, deployment changes, and provider limits can leave gaps; deduplication is best-effort. Local development runtime logs aren't supported.
UP AND RUNNING, SIMPLY
Connect what you need, keep the context close, and let the app stay out of your way.
Choose the installer for your OS and architecture. Open Simply Logs when you want to monitor.
Add an application, connect a provider account, or enter a public HTTPS URL for health checks.
Browse available recent history, then follow new activity. Reuse a saved token for other apps on the same provider.
WHAT'S NEW · v1.1.0 ·
Version 1.1.0 catches runtime error spikes, waits for a real outage before raising a health alert, and takes you straight to the logs behind every alert.
For Vercel, Netlify, and Render connections, get alerted when live runtime logs show 5xx responses or error output at a per-minute rate you choose: 3, 5, 10, or 25. Isolated errors and loaded history never alert.
Choose how many failed health checks in a row trigger an alert: 1, 2, 3, or 5.
Mute straight from an alert toast. Muted apps appear in alert settings with the time remaining and an Unmute button.
Toasts, Recent Notifications, and desktop banners focus the window and select that app, switching projects if needed.
Every alert shows the app's environment and provider, such as “production · Vercel”, including in desktop banners.
Recovery alerts report how long the incident lasted and how many failures it included, such as “Down for 2m 15s · 9 failed checks”.
Health checks now alert after 2 consecutive failures by default instead of on the first one, so a single failed 15-second check no longer triggers an alert. Set the threshold to 1 in alert settings to restore the previous behavior. Failed deployments still alert immediately.
PRIVATE BY DEFAULT, CLEAR ABOUT STORAGE
There is no Simply Logs hosted logging backend. The desktop app connects directly to provider APIs and streams.
Credentials: saved tokens use OS-backed encryption when available. Otherwise they remain session-only and need re-entry after restart.
Logs: the newest 1,000 entries across projects are saved locally and restored after restarts. This history is not encrypted and may contain sensitive output.
Control: clear selected-project history or delete its application/project. Clearing local logs does not delete provider history; future restarts may backfill recent logs again.
GET THE DESKTOP APP
Simply Logs runs on your computer. Pick the package that matches your operating system and processor.
Packages appear here when the corresponding build is published. Unsigned installers may trigger operating system warnings.
GOOD TO KNOW
Clear answers about what the app does — and where provider limits apply.
Yes. Public URL mode checks a public HTTPS endpoint every 15 seconds. Reported health, latency, and failure rates describe those probes, not overall application throughput or request performance. It does not retrieve application logs and needs no provider token.
Vercel connections include deployment status, recent build logs, past-hour runtime history, and live serverless and edge runtime output. Netlify connections include deployment status, past-hour Function and Edge Function history, and live runtime output; Netlify build logs remain in its dashboard. Render connections include service deployment status, build logs, and past-hour plus live app/request logs.
Connect a Render API key and discover a service to monitor its deployment status, retrieve build logs, review up to 1,000 app/request log entries from the past hour, and follow live app/request logs. Render's log API is time-based, so build output queried from the latest deployment's creation time can include nearby deploys; runtime logs are scoped to the selected service, not a particular deploy. Static sites do not emit runtime logs. Availability depends on service type, workspace plan, retention, and API-key permissions.
No. History and live streaming are separate capabilities, not guaranteed complete ingestion or permanent cloud retention. Access depends on token permissions, provider retention, plan access, and query limits. Vercel history is capped at 1,000 runtime requests per selected environment and can include previous deployments. Netlify history is for the deployment selected on connection, not earlier deployments from that hour, and is capped at 1,000 lines across sources. Render history is capped at 1,000 app/request entries for the selected service.
Up to 10 Functions per application are monitored, selected alphabetically; additional Functions produce a warning. Edge Functions use a separate stream. Partial source failures do not stop working feeds. Netlify build logs remain in its dashboard.
Yes. Applications using the same provider can reuse one saved token, even across projects. Team, workspace, and application settings remain independent. The Access token list shows each saved credential once, labeled with an application that uses it; selecting one does not reveal its value to the renderer. Editing or deleting a project or application preserves credentials still used elsewhere; removing the last reference deletes that token. Session-only tokens can be reused until the app exits, then must be entered again.
Yes. Choose Edit current project in the project selector or use the sidebar pencil button. Name, description, color, and tags can be edited or cleared without recreating the project, removing applications or logs, or resetting monitoring and filters.
Monitoring runs while the app is open with a window and stops when paused. Runtime entries arrive as providers send them. Deployment selection refreshes roughly every 30 seconds; failed history queries and streams warn and retry automatically.
Credentials use operating-system-backed encryption when available; otherwise tokens are session-only and must be re-entered after restart. Saved log history is local and is not encrypted, so it may contain sensitive application output. The newest 1,000 entries across projects are restored after project switches or app restarts; restored history does not trigger fresh alerts or count as live throughput. Storage failures are reported.
HTTP method badges are shown when provider metadata includes a method. That makes preflight OPTIONS and the actual POST request distinguishable even when they share an endpoint. Methods are searchable regardless of case and are included in copied text and JSON exports; build messages and other entries without method metadata are not assigned an invented method. Vercel console messages are grouped per request, with individual messages and metadata retained in details and exports.
Unsigned installers may show warnings from your operating system. Review the publisher and source before installing; never disable your security protections to install an app.
WHEN YOU NEED A CLOSER LOOK
Vercel, Netlify, Render, or a public URL. Your logs stay close to home.