One view of services
Availability, capacity and certificate expiry alongside service ownership.
All projects
MONITORING / INFRASTRUCTURE / RESPONSE
Rewinit PULSE
Know what works and what needs attention.
We are developing a shared view of service and infrastructure health. PULSE is intended to help small teams notice problems, understand their impact and notify the person responsible for responding.
Delivery preparation
A plan that leads to deployment.Delivery preparation
As of 28 October 2026Scope defined. Next step: delivery.
We have prepared the project identity, first-version scope and acceptance criteria. The next stage is to build and verify the described journey with a partner. Timing will be agreed for the selected deployment.
- Prepared
- Scope and identity
- 01 / Next stage
- A selected-service dashboard, HTTP, capacity and certificate checks, and one notification channel.
- 02 / Planned stage
- Partner pilot
Who are we building this for?
Small IT teams and businesses using external server administration.
Where do we begin?
Outage notices, expiring certificates and capacity warnings sit in different tools. PULSE will connect selected signals with a service inventory and clear response rules.
What will the first version include?
IT dashboard and care / Rewinit PULSE
Alerts with context
Notifications are intended to identify the service, the breached condition and the agreed response path.
A history of state changes
The start of an issue, acknowledgement and recovery in one timeline.
Explore the planned journey.
Choose successive steps to see how the project’s first application is intended to work.
Interactive delivery plan
Rewinit PULSE / 01
Collect signals
Example scenario
TEST-API and an example availability check.
Planned outcome
The service inventory links each check to its responsible team.
An example scenario using prepared data. This presentation illustrates the planned process; it does not operate external systems.
A plan that leads to deployment.
Each stage follows verification of the previous outcome. The pilot scope will be agreed with a partner.
Prepared
Scope and identity
Project mark, visual direction, audience, first-deployment scope and acceptance criteria.
- 01
Next stage
First version
A selected-service dashboard, HTTP, capacity and certificate checks, and one notification channel.
Acceptance criterionA controlled outage opens one incident, an alert reaches the recipient and service recovery closes the event.
- 02
Planned stage
Partner pilot
Tune thresholds against a partner’s test service set and verify responses to simulated outages.
- 03
Planned stage
Preparation for availability
Agreed support hours, escalation, rule reviews and environment health reporting.
Development journal
Rewinit PULSE / DEVELOPMENT
First-deployment scope and identity prepared.
We have prepared the project mark and visual identity and defined its audience, first scenario, milestones and acceptance criteria. The delivery plan describes the next outcome to verify.
Project identity
A distinct mark and colour within the shared Rewinit system. The identity accompanies the project from planning to first-deployment materials.
Download SVG logoRewinit PULSE / PARTNERS
Build the first deployment with us.
We are seeking a partner to adapt the scope to a specific process and evaluate the outcome in a pilot.
Discuss PULSEA useful starting point
- A service list and its owners
- Access to agreed measurements
- An alert channel and support hours