Core Features
This page reflects the actual backend and frontend behavior in the repository today.
The strongest current feature areas are:
- architecture-based project creation
- repo-driven app delivery
- managed single-database provisioning
- project workspace operations
- SonarQube access and code-quality summary
Architecture-Based Setup
The current product starts with architecture selection, not with one generic deployment form.
Available paths:
| Path | Current focus |
|---|---|
| Monolithic | One repo, one deployable app, fuller lifecycle controls |
| Microservice | Repository selection plus service-oriented setup |
| Database | Managed database provisioning and runtime operations |
Keycloak-Backed Authentication
A8S uses Keycloak for session and identity handling.
Current behavior includes:
- brokered sign-in flows
- session-aware redirects when Keycloak has expired
- profile sync between the frontend experience and backend profile APIs
- provider-avatar fallback when a custom avatar has not been uploaded
Repository-Driven App Delivery
For monolith and microservice work, repositories are central to the current product.
What is implemented today:
- GitHub and GitLab repository selection in app flows
- project ownership and user-scoped resource access
- platform-driven deployment orchestration after project setup
- webhook and auto-deploy support in the monolith flow
Depending on your deployment environment, the platform pipeline can integrate with:
- Jenkins
- container registry storage
- Kubernetes rollout logic
- GitOps-oriented cluster sync tooling used by operators
Monolithic Release Operations
Monolith projects currently expose the richest release-management path.
Implemented features include:
- repository connect/import flow
- webhook lifecycle management
- auto-deploy toggle
- manual sync
- release listing
- rollback
- custom domain management
- delete
Microservice Project Operations
Microservice projects currently emphasize:
- repository-first setup
- service-oriented configuration flow
- live project details
- readiness checks
- domain updates
- delete
This is real product functionality, but it is not yet the same kind of fully detailed per-service runtime control plane that older docs implied.
Managed Database Operations
The current database flow is one of the most distinctive A8S features.
Implemented today:
- self-service database provisioning
- connection profile and credentials
- built-in browser console
- backup settings and history
- manual backup trigger
- restore
- download
- delete
Supported current single-db engines:
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Cassandra
- Oracle Database
- Microsoft SQL Server
The frontend currently exposes single-instance database provisioning as the active self-service path. A cluster mode exists conceptually, and cluster-related backend modules are present, but the main database setup screen marks cluster mode as unavailable right now.
Backup & Restore
Single-db backup and restore is implemented with engine-aware formats.
Examples in the current backend include:
- PostgreSQL: SQL dump archive
- MySQL: SQL dump archive
- MongoDB: BSON archive
- Redis: RDB
- Oracle: Data Pump dump
- SQL Server: backup file
- Cassandra: export bundle
The current UI already supports:
- backup history
- restore
- download
- remove
SonarQube Access
The backend exposes project-scoped SonarQube support through dedicated APIs.
Current capabilities:
- fetch project SonarQube summary
- provision dashboard access for a project/user pair
This is more accurate than describing SonarQube as a vague future idea. It is already part of the project surface.
Workspace Tooling
The dashboard includes operational pages for:
- projects
- deployments
- notifications
- monitoring
- logs
- image scanner
- profile
- settings
Some of these pages are already backed by live project or deployment data, while others still mix live state with local/mock preview data.
Avoid describing the current dashboard as a complete Prometheus + Grafana + Loki + Alertmanager control center. The present UI is more of a workspace operations surface than a full observability suite.
Custom Domains and Routing
Domain management is real in the current product:
- monolith domain set and sync exists
- project/workspace domain sections exist
- wildcard DNS is already part of how generated platform hostnames can be handled
- TLS-backed runtime routing is part of the database and app exposure flow
What Is Not Ready to Document as Fully Shipped
Older docs overstated a few areas. Based on the current repo, do not describe these as fully delivered end-user features:
- universal dev/staging/prod environment promotion across all project types
- full Vault-only secret injection as the active implementation everywhere
- a public production-ready A8S CLI
- a full built-in testing suite tab with load/stress/smoke/failover execution
- fully live Harbor vulnerability management inside the current scanner UI