AFTER DARK DOCS

Documentation / Start here

Build, operate, and get help.

A practical guide to After Dark Systems services and the account that connects them.

01 / Basic services

One account, focused platforms.

API

Public integrations live at api.afterdarksys.com. Private endpoints require an authenticated service identity.

API reference →

DNSScience

DNS analysis, validation, and automation are hosted separately at dnsapi.ai.

Open DNSScience →

CDN

Managed content delivery backed by Bunny CDN, with configuration available through Client Central.

CDN service →

Status

Current service health and incident updates are public. Check status before opening a ticket.

Service status →

Billing

Review subscriptions, invoices, payment methods, and service entitlements in the billing portal.

Billing portal →

Open source

Browse supported public projects, documentation, licenses, and source repositories.

OSS index →

02 / Portal guide

Your services control panel.

Sign up once, verify your email, then use Authentik SSO across After Dark Systems. Customers enter Client Central; employees enter Employee Central based on their assigned Authentik group.

  1. Create an accountRegister at signup.afterdarksys.com.
  2. Verify your emailUse the time-limited link sent by the identity service.
  3. Sign in with SSOContinue through adsas.id; never create a second local password on a service.
  4. Choose a serviceYour panel shows only the products and environments your account can access.

03 / Getting help

Send the right signal.

Service unavailable?

Check the public status page for an active incident or scheduled maintenance.

Check status →

Account or product issue?

Open a support ticket with the service name, time, request ID, expected result, and actual result. Never include passwords or API secrets.

Open a ticket →

Track engineering work?

Authenticated customers and staff can follow approved work and changes in the ticketing system.

View Changes →

04 / Security incidents

Report suspected security issues privately.

Do not post vulnerabilities in forums, the public wiki, or a public source-code issue. Open a security incident ticket and include the affected service, observed time and timezone, impact, safe reproduction steps, and a way to contact you.

Do not attach live credentials, access tokens, private keys, personal data, or malware. State what evidence you hold and the security team will arrange a protected transfer.

Report a security incident