Linux, Docker, and operations you can explain
Palmate Solutions helps businesses host and operate software on Linux servers, VPS environments, and cloud platforms. We work with Docker and Docker Compose, reverse proxies, monitoring, backup strategies, and deployment pipelines. The goal is an environment a competent engineer can understand at 11pm — not a unique snowflake that only the original installer can touch.
Packages were installed by hand two years ago. We prefer declared configuration, compose files, and notes for DNS, TLS, and secrets.
A backup you have not restored is a rumour. We define what is backed up, where it lives, and a restore drill.
Copying files over SSH works until it does not. We add a pipeline, health checks, and a way to roll back.
‘The site is usually fine’ is not an SLO. We help you pick a target that matches budget, then instrument it.
Users, firewalls, unattended upgrades where appropriate, and a baseline that is not the default SSH-on-22-with-password story.
Containerised apps, networks, volumes, and compose files that match how you actually run staging and production.
Nginx or similar in front of applications, with certificate issuance and renewal that does not depend on a calendar reminder.
Health checks, disk and certificate alerts, backup jobs, and CI/CD that deploys artefacts — not a live-edited server.
What runs where, who has keys, what a day of downtime costs, and what compliance actually requires.
Access, updates, firewall, and secrets. No application work on an untrusted box.
Containers or otherwise repeatable builds, a staging twin, and a deploy path.
A restore test, basic dashboards, and on-call notes. Then we iterate.
A growing site that needs SSH, Docker, and scheduled jobs that shared hosting will not allow.
App, worker, and database as services with documented volumes and backup commands.
The application stays; the access model, TLS, and backup story catch up.
No. Most business applications of this size are better served by Compose on a well-run VM or a managed platform. Kubernetes is a tool for a specific operational need, not a badge.
A VPS is often enough and cheaper to reason about. Managed cloud earns its keep with specific services (object storage, managed databases) or traffic patterns. We compare them against your actual constraints.
That is a separate operations agreement, not an implied feature of a setup project. We can design for a provider or an internal owner to take the pager.
Yes. We prefer least-privilege access and an audit of what already exists before adding more services.
Next step
Share the current system, the constraint, and the outcome you need in the next quarter. We will say if Palmate is a fit.