Export redirect configs to any platform

Config export reads your redirect rules and translates them into production-ready configuration syntax for your target server. Each export target has a dedicated code generator that understands the idiomatic syntax, directive ordering, and escaping rules for that specific platform.

For Nginx, the generator produces full rewrite blocks and map-file variants (exact and prefix). For HAProxy, it generates ACL-based configurations and map-file variants. CSV export provides a universal spreadsheet-friendly format. All outputs include comments showing rule metadata.

Exports can be scoped to a single project, a filtered subset of rules, or your entire rule set. The API endpoint allows you to integrate config generation into your workflows, so your server configurations stay synchronized with your redirect rules.

Managing redirects across multiple servers typically means maintaining separate configuration files for each — an Nginx config here, an HAProxy config there. Config export eliminates this duplication by letting you manage all rules in one place and generate server-specific configs on demand.

Each generated configuration includes comments with rule metadata — the rule name, creation date, and priority — so the output is human-readable and debuggable. Syntax validation runs before output, ensuring the generated config will parse correctly when loaded by the target server.

The selective export feature is particularly useful for agencies and teams managing multiple projects. You can export rules for a single domain or project, share the config with a client, and keep other projects private. The API allows programmatic export for integration with your deployment workflows.