This document provides a comprehensive overview of our infrastructure setup, focusing on our AWS organization structure, account management, and access procedures.

We use AWS ElastiCache for Valkey as our primary caching solution across all environments. Valkey is an open-source, Redis-compatible in-memory data store that provides high performance and reliability for our applications.

What

Why we cache bots

Overview

Introduction

Introduction

This documentation describes our previous self-hosted GitLab runners on Hetzner Cloud. As of January 2025, we migrated to Cloud Runner for managed runners.

Laravel Cloud is our deployment platform, replacing Laravel Vapor for hosting Laravel services. Not all projects are on Cloud yet - we're migrating incrementally.

Performance comparison between Laravel Vapor and Laravel Cloud.

Overview

This document describes how the Zoo environment is configured to support Playwright testing across multiple domains, specifically for use by both Volpe and Criceto projects.

We use Cloud Runner for our GitLab CI/CD runners. They provide fully managed runners so we don't have to maintain our own infrastructure.

Sent to Ryan: Google Doc

Step-by-step guide for migrating Laravel projects from Vapor to Cloud. For Cloud-specific configuration patterns and known gotchas, see the Configuration Reference in the Laravel Cloud overview.