OSM Linux EngineersContact Us
MainHomeServicesPricingCase StudiesGuidesAboutContact
Service categoriesServer & OperationsWeb StackContainersDatabasesCloud & IaCSecurity ReviewsDevelopment & AutomationNetwork, DNS & CDNBackup, Monitoring & SecurityMigrationsFor AgenciesAll Services

Send enquiry

Tell us what you need help with

Use this short form to describe the issue, request or project. We will reply with the best next step, likely scope and any access details needed.

Not sure which option fits? Choose “Not sure” and we’ll suggest the most suitable route after reviewing your enquiry.

Please do not send passwords, secret keys or private access details through this form. If access is needed, we will confirm a safe method after reviewing the enquiry.

Prefer email? contact@osmlinuxengineers.com

What helps

Keep the first message short

The affected website, server, container, cloud account, database or service
Whether this is planned hourly work, a fix, a review, a migration, ongoing support or an urgent issue
A short description of the issue, request or project goal
Any error messages, screenshots, failed commands or monitoring alerts
Recent updates, deployments, migrations, DNS changes, configuration changes or work already attempted
Whether the system is production/live and the business impact

Process

How support works

Pricing is clearer when the issue, risk and access requirements are understood before production work starts.

1. Send the issue

Tell us what you need help with, what system is involved, the business impact and any useful context.

2. We confirm the right route

We suggest emergency support, a fixed technical fix, an infrastructure review, a migration project or a retainer.

3. Scope and payment are agreed

Fixed-scope work is agreed before starting. Emergency work starts with the minimum support window.

4. Secure access and handover

We use temporary access where possible, provide progress updates, and send a practical handover note after the work.

Secure access

Secure access when it is needed

We do not need passwords in the first enquiry. We can often start with logs, screenshots, error messages or configuration snippets. If access is required, we agree the safest method first.

Linux servers

Use a temporary SSH user and our public SSH key where possible. Sudo access should only be granted when the work requires it.

AWS accounts

Do not send root credentials. Use scoped IAM access, IAM Identity Center, or a temporary role. Reviews can usually start read-only.

Internal tools and operational dashboards

Create temporary admin users for WordPress, Cloudflare or other dashboards, then remove them after completion.

Passwords

If a password must be shared, use a one-time secret link or password manager share. Do not send passwords directly by email.