Get the server out of the back room, and keep someone to call

Windows and Linux virtual servers in our Austin data center, for your apps, internal tools and remote staff. We run the servers, test that the backups restore, and an engineer answers when something breaks.

Talk to a consultant
Your office server
Moving
Run by Petrichor engineersVirtual servers
  • Windows file serverRunning
  • Linux app serverRunning
  • Accounting databaseMoving

What belongs here

  • The servers in your office, moved somewhere someone looks after them.
  • Apps and internal tools that need to stay up, including an app you built with AI tools.
  • Teams that want isolation they can explain to their own customers.
Fiber patch panel with blue and orange jumper cables.

What we handle, what you keep

We install and configure the servers, operating system, databases and services you need, then handle patching, backups and restore tests, monitoring and the changes your team requests. Your team owns the application and its releases.

Your developers
  1. Build
  2. Test
  3. Release
Petrichor engineers
  1. Restore ticket
  2. Restore from backup
  3. Ticket closed

Virtual servers by default

Your applications run on virtual machines by default, for portability and redundancy.

  • Any Linux or Windows.
  • Any database that runs in a virtual machine, including MySQL, MariaDB, PostgreSQL, Microsoft SQL and ArangoDB.
  • Docker and Kubernetes for containerized applications.
  • Hosted desktops for remote staff.
  • Your own network segment.

Business continuity

  • Full-system image backups, taken weekly.
  • Daily file backups, and application-aware backups for your databases.
  • Backups kept on storage separate from your production servers.
  • Replication to a second location of your choosing.

Right-sizing

Engineers monitor load and resize servers up or down on request, and predictable billing means servers can simply stay on. Kubernetes handles application-level elasticity.

Colocation on a Petrichor-style stack

  • Self-managed: your own segregated hardware, built like Petrichor, managed by your team.
  • Trinsic-managed: the same setup, with Trinsic supporting it.

Colocation on bare metal

  • Self-managed: dedicated hardware, managed by your team.
  • Trinsic-managed: dedicated hardware, with Trinsic supporting it.

Compare your options

Server in the officeBig public cloudPetrichor
HardwareYou buy it, and replace it every few yearsThe provider's, shared by default, dedicated at extra costOurs, in our Austin data center, in your own network segment
Server managementYour staff or an IT vendorYour team, or managed services at extra costPetrichor engineers, as hands on as you choose
Monthly billPower, cooling and upkeep, plus the next hardware purchaseUsage based, so it moves with traffic and settingsA predictable monthly rate set in your service agreement
Data transfer feesNone, within your office connectionCharged for data going outNone
Who you callWhoever set it upSupport, priced by planThe engineers who run your servers

Moving from a public cloud or VMware

We rehearse the move on a copy first, test it with your team, then cut over on a date you pick.

Runs todayPublic cloud
RehearsalCopy on our hardwareTested with your team
LivePetrichor
On the date you pick

Tell us what you're running and where

It’s a thirty minute call with a consultant. Bring what you’re running and what you need it to do.

What you’re running, where it runs today, and what you need it to do. Leave out passwords and customer records.

We use these details to reply to your request. Website privacy notice

Talk to a consultant