Business solutions
LaravelPHPFilamentMySQL
Laravel and Filament when a real back office is needed — roles, permissions, document generation. SPEIA Gestion at ODS Logistique and SPEIA Immo at Odimo both run on it, with MySQL.
Hosting & support
Your SPEIA solution, hosted and supported by the people who configured it
Go-live and support are planned together from the start. You know who hosts your solution, how it evolves and how to recover your code if you change providers.
In practice
What actually changes
01
An isolated space per client
Every solution gets its own folder, process and virtual host on our OVHcloud server in France. Server resources are shared; capacity and availability needs are agreed during scoping.
02
One-command go-live
The build is verified before going live. If it fails, the previous version keeps serving. The same command gives the same result, at any hour.
03
A preview to sign off
Changes are reviewed on a preview URL before approval. Non-indexing is not access control: confidential data requires dedicated protection.
04
Automatic HTTPS, backups and restarts
Certificates renew themselves, timestamped backups run before every release, and the process restarts on incident.
05
Support, not a fresh quote
A fix, a wording change, a question: it's part of the relationship. You reach us directly.
06
No lock-in
The code is yours. Standard technology, full archive and deployment documentation handed over on request. You stay because it works, not because you're trapped.
Your solution won't be hosted at your provider's provider.
Elsewhere
With us
The tool is delivered, hosting is your problem.
Your solution runs on our server, the one we administer every day.
The certificate expires on a Sunday and nobody picks up.
Automatic renewal, automatic restart, and an alert on our side.
Changing one label takes a quote and two weeks.
Fixes, changes and questions are part of the relationship, not a fresh quote every time.
First-line support reads you a script.
The person who answers you is the one who configured your solution.
Nobody knows where the backups are, or whether they work.
Timestamped backup before every release, restore tested.
Technical sheet
What actually runs under your solution
None of these lines is decorative: this is the exact configuration of the machine our clients' solutions live on.
- Server
- OVHcloud, France. Infrastructure managed by our team. Any third-party services are described in the privacy policy.
- Isolation
- One folder, one process and one virtual host per client. Hardware resources on the server remain shared between solutions.
- Web server
- nginx at the front, with permanent HTTP-to-HTTPS redirection and compression enabled.
- Certificates
- Let's Encrypt, renewed automatically. Renewal status is checked during maintenance.
- Process supervision
- PM2: automatic restart on unexpected exit, and relaunch when the server reboots.
- Go-lives
- A single repeatable script: install dependencies, build, verify, restart. If the build fails, the previous version keeps serving.
- Preview
- A separate HTTPS address with a no-index header and a closed robots.txt. What you approve is exactly what goes live.
- Backups
- Timestamped archive before every production release, with retention. The old version is kept, not overwritten.
- Scheduled jobs
- Monitored scheduler with automatic catch-up and periodic reporting — a job that stops running gets noticed.
- Domain switch
- Certificate issued before the switch, production vhost tested, DNS change reversible. Your current tool stays live until the last moment.
Tech stack
What we actually use, and why
Not a logo wall: every technology below runs a solution in service or this site. What we don't run in production, we don't list here.
Interfaces
Next.jsReactTypeScriptTailwind CSSNode.js
Interfaces that need to load fast and rank natively — this site's stack, with Node.js handling server rendering.
Infrastructure
Ubuntu ServernginxPM2Let's EncryptOVHcloud
The server we administer ourselves every day (technical sheet above): nginx reverse proxy, PM2 process supervision, self-renewing certificates.
Documents & integrations
DomPDFOpenSpoutAPI INSEETâches planifiées
What the tools in service produce every day: agreements, attendance sheets and invoices as PDF, spreadsheet exports, company checks by SIRET against the INSEE registry, scheduled reminders and follow-ups.
Engineering background
JavaAdobe Experience ManagerPHPLinuxApache
Hands-on IT since 2002 and a company in business since 2010: first ten years on large-scale Java content platforms (Adobe Experience Manager), then PHP and Linux server administration, before today's business solutions. None of it is sold by default — it is what lets us take over an existing system, whatever it is, and plug into it rather than rebuild everything.
Cadence
What gets done, and how often
We don't advertise an uptime percentage: nobody can honestly prove one at this scale. Here instead is what actually runs, and when.
- Infrastructure monitoring
- Continuous
- Backups
- Daily
- Full backup before production release
- Every go-live
- Server security patches
- On release
- HTTPS certificate renewal
- Automatic
- Backup restore test
- Quarterly
You are not locked in
The code is yours and lives in a repository you have access to. The server configuration is documented and handed over. Another provider can take your solution on without calling us. We don't hold your tool: we just run it better than anyone else.
Frequently asked
Am I locked into your hosting?
No. The code is yours and is handed over. We use standard technology — nginx, Node, PHP, Laravel — that any provider can pick up. If you leave, we hand you the full archive and the deployment documentation.
What happens if the tool goes down?
The process manager restarts the application automatically. If the problem came from a release, we roll back to the previous version. You reach us directly, with no first-line support reading from a script.
Can I keep my current domain name?
Yes, and that's the usual case. We prepare your solution on a preview address, you review it calmly, and the domain switch is a single DNS change with the certificate already issued. Your current tool stays live until the last second.
