GitAscii Pro Overview

GitAscii Pro extends V2 publishing with multiple profiles, versions, dynamic rules, publication health, error records, and analytics for a separate README badge. The normal profile SVG is hosted on the user’s gitascii branch; visiting the README does not call GitAscii’s rendering service.

Editor → gitascii branch: configurations + dark/light SVGs
        → GitHub Action refreshes SVGs → optional OIDC health report
README → raw.githubusercontent.com profile SVGs
       → optional gitascii.com/api/badge/username → badge request metrics

Pro features

Feature	What it measures or controls
Profiles and versions	Publish named profile slugs, duplicate designs, inspect revisions, and restore a saved version.
Dynamic rules	Choose a profile for the default HTTP API embed when `?dynamic=1` is enabled; static raw GitHub URLs do not switch at request time.
Analytics	Counts requests observed by the separate badge endpoint, usually GitHub Camo cache refreshes. These are not exact human views or unique visitors.
Health and errors	Receives authenticated GitHub Action reports about publication runs and failed external assets. The health badge displays that reported state.
Alerts	Records error-alert logs subject to settings and cooldown; the current widget-error path does not send email.

The dashboard routes include /pro, /pro/analytics, /pro/health, /pro/profiles, /pro/reports, /pro/errors, and /pro/emails. See account, access, and limits for one-time payment activation, profile limits, refresh settings, and legacy subscription behavior. Declared entitlement flags do not by themselves establish a customer-facing feature.

Storage and trust boundaries

When DATABASE_URL is configured, PostgreSQL stores persistent profile and Pro data; Redis supports caches and some telemetry operations. Without a configured database, Redis is used for several stores, with an in-memory development fallback. GitHub remains the source of the published configuration and SVG files. The GitHub App token authorizes publication; the Action sends Pro health reports using a verified GitHub OIDC token. For the limits of analytics, see Telemetry & Privacy. For README embeds, see GitHub README Integration. See alert implementation limits and daily health score semantics before interpreting dashboard status.

Getting Started

Architecture

Engine and Configuration

GitAscii Pro

Widgets Overview

Essential Widgets

ASCII and Cards

Stats & Metrics

GodProfile Suite

ASCII Profile Suite

Control Plane Suite

Codeweb Aura Suite

External Integrations

Premium ASCII Suite

Surveillance Suite

Windows XP Suite

Minecraft Suite

Templates

Development Guides

Reference

GitAscii Pro Overview

Pro features

Storage and trust boundaries

​Pro features

​Storage and trust boundaries

Pro features

Storage and trust boundaries