Status
Service status
The status of what LIVING SOFTWARES keeps alive. A company that says “we stay” must be able to show it.
The site's pulse, at rest58 beats per minute
After delivery, we stay.
Most sites stop being maintained once they are delivered. We built our model the other way round.
Going live
Your system goes live after acceptance testing, security tests and the training of your teams.
Included support
Every delivered project includes 3 months of support (1 month for Essential). For 90 days, any defect within the agreed scope is fixed free of charge.
Your support level
After that, you choose: a level of the Living Contract, with no commitment of more than 12 months, or you take your system over yourself, which you confirm to us in writing.
Every month, a page
The monthly report says what was measured and what was done.
What we monitor.
For every site, application and agent we maintain, five things are tracked. What each one covers depends on your support level.
Availability
We check that your system responds. A blocking outage is acknowledged within the time written into your level.
All levels · 24 hours a day from Growth
Hosting and backups
Your system is hosted and backed up by us: weekly, daily, or daily with replication, depending on the level.
All levels
Security updates
Security patches are applied to your system and counted in your monthly report.
All levels
Domains and certificates
A domain name that expires, a certificate that lapses, and your site becomes unreachable, or is shown as dangerous. We monitor both.
All levels
Your automations and your agents
Supervised, repaired when a third-party service changes its interface, and tuned continuously.
From Growth
The Living Contract, line by line.
Three support levels, three rhythms. Every line is written into our offers; the prices are on the Pricing page.
| Commitment | Watch | Growth | Partner |
|---|---|---|---|
| Availability monitoring | Included | 24 hours a day | 24 hours a day, with on-call cover |
| Backups | Weekly | Daily | Daily, with replication |
| Security updates | Included | Included | Included |
| Domain and certificate monitoring | Included | Included | Included |
| Blocking outage | Acknowledged within 8 working hours | Acknowledged within 2 working hours | Acknowledged within 2 hours, 24 hours a day |
| Target availability | 99.5% | 99.5% | 99.9% |
| Changes included | 1 hour per month | 4 hours per month | 12 hours per month |
| Supervision of automations and agents | Not included | Included | Included |
| Repairs when a third-party API changes | Not included | Included | Included |
| Monthly report | Simplified | Full | Full, with analysis |
Several brands or a complete system: a bespoke contract is built with you.
One page, every month.
Every month, every subscriber receives a page. No jargon: figures measured on your system, and what we did.
What the page says
- Your site's availability over the month
- Security patches applied
- Interruptions, and their repair
- For an agent: conversations handled, leads passed to your team
- The estimated time saved for your teams
How detailed it is depends on your level: it is the “Monthly report” line in the table above.
This document is what justifies your subscription — not our word.
This site, as it is served.
We apply to our own site what we sell. Each line below is read from this version when it is built, or checked against its code before every release.
Where it lives
- Version
- Version of 19 October 2026
- Built that day on the server that serves it, verified before its release, then checked live.
- Hosting
- Germany, European Union
- With Hostinger International Ltd, as our legal notice states.
- Encryption
- HTTPS only
- The browser commits never to go back to an unencrypted connection for two years, subdomains included.
What it protects
- Code
- No outside scripts
- The browser runs only the code the site serves; its inline scripts are allowed one by one, by their fingerprint.
- Framing
- Never inside another site
- None of its pages can be displayed inside another site.
- Permissions
- Microphone, camera, location: blocked
- The site cannot even ask for them.
- Data
- No cookies
- No audience measurement, no advertising. A technical log of requests, kept for 90 days at most, for security.
How it is built
- Technologies
- Next.js 16 · React 19
- In strict TypeScript. The site's matter is drawn in WebGL2, written by hand.
- Rendering
- Readable without JavaScript
- Every page is rendered in advance: the text arrives whole, even without a script.
- Fonts
- 3 families, 66,772 bytes
- Served by the site itself, with no outside service, and checked by fingerprint.
- Contrast
- 39 colour pairs
- Recalculated with every version, and all meet their threshold: at least 4.5:1 for text, 3:1 for a line that carries meaning.
- Pulse
- 58 beats per minute
- The resting rhythm of the site's line: calm, human, confident.
Checked at every release
- BuildThe code is checked by machine: strict typing, coding rules, tests, calculated contrasts.
- BuildThe public version is built twice: the second build proves that the security policy describes exactly the scripts served, and that no style is written inline.
- ReleaseEvery page in the sitemap must respond; an unknown address must return a 404 error.
- ReleaseThe seven security headers must be present.
- ReleaseThe fonts served must match their fingerprint, to the byte.
- ReleaseIf anything fails, the previous version comes back on its own.
Measured here soon.
An external probe will measure this site continuously. Its readings will appear on this page as they are, bad days included:
- Availability, over thirty days
- Response time
- Incidents, and what we did about them
Until then, none of these figures is written by hand: a dashboard painted green would prove nothing.