Trust and deployment

Where Peertic review data goes.

Peertic is available for self-hosting. Dedicated hosting can be arranged on request. The data path and operating responsibilities depend on your choices. This page explains the product demonstrations and the questions to settle before a rollout.

Discuss your requirements

Self-hosted data path

The CLI, automation server, configuration, and review history run in infrastructure you administer. Review context goes to the model endpoint and integrations you configure. Release builds also contact Peertic’s license service for seat admissions.

See deployment options →

Hosted data path

Dedicated hosting can be arranged on request, with its location and operating responsibilities agreed for your deployment. Confirm network access, storage, backups, retention, support, and model-provider terms for the proposed configuration before signing.

Ask about hosting →

Configurable controls

Teams can configure models, prompts, review scope, severity thresholds, and project rules. Telemetry is off by default; when enabled, it can use console output or a configured OpenTelemetry collector. The admin portal listens on localhost by default.

Explore controls →

Website inquiries

The public contact form is separate from the product data path. It uses Cloudflare Turnstile to reduce spam, and inquiries are stored in a restricted-access business record and sent to the team handling them by email.

Read the website privacy policy →

Product workflow

See Peertic in use

Explore how Peertic connects pull requests to requirements, reports findings in GitHub, and tracks review sessions in the portal. Inspect the recorded payment retry example to see its GitHub comment and check, test-backed fix, and AI assistant triage of the follow-up.

Inspect the recorded example →

Who operates Peertic

A named business contact

Peertic is a product of Wingdium Technologies. For product, commercial, or privacy inquiries, email support@wingdium.com.

Learn about Wingdium Technologies →

Before you deploy

Request a written evaluation scope.

Ask for a walkthrough of your review workflow and a written proposal covering deployment responsibilities, the model and integration data path, licensing, pricing, support, and data terms. Additional privacy documentation, deployment-specific data-flow details, and security assessment materials can be provided on request.

Start a conversation