Postgres On-Premises Setups

There are many reasons to run Postgres on-premises:
  • Cost saving
  • Access to unavailable Extensions
  • Optimized performance with a bare metal setup
  • Compliance with privacy regulations

Challenges

  • Automation for critical tasks like backup and recovery.
  • Integration of additonal components for monitoring, connection pooling, load balancing etc
  • Automatize Operational Tasks like PITR for support or analysis

My Approach


I build your Setup as Code with Ansible and provision it within your environment.
You receive documented setup code, giving you full transparency and the following benefits:
  • Repeatable, documented setup
  • No vendor lock-in. You own the code.

Flexible support model – You decide whether I:
  • continue supporting you in provisioning and production operations,
  • leave operations fully in your hands, or
  • hand over to third parties for ongoing support.

Process

Step 1

Setup Definition

  • Pick one of the predefined Setups
  • Or we define a tailored setup together based on your requirements

Step 2

Setup Delivery

  • I prepare your setup as well as required Operational Task automatizations.
  • Setup Code and Documentation delivered.

Step 3

Setup Validation

  • Testsystem Provisioning
  • You test if everything works as expected

Step 4

Going Live

  • Productionsystem Provisioning
  • Optional Near 0 downtime Migration from existing Setup

In Production

Live Operations

You can decide if you want to have my continued support or if you operate on your own.

Setups

Variant 1

Basic

  • Grafana/PgWatch: Monitoring
  • PgBackRest: Encrypted Backups on S3, Azure, and GCS Compatible Object Store
  • Optional: PgBouncer
  • Optional: Periodic Backup Verification
  • Operational Actions:
    • PITR Recovery to separate Machine or Docker
    • Backup Recovery

Variant 2

Individual

I develop setups tailored to your specific requirements.
Start the Conversation