Private operator console.

MerTekStak

Manage configured platforms.
Verify builds before release.
Review cloud operation plans.

MerTekStak is the control plane for MerTekCore-based platforms. It keeps platform configuration, cloud environments, build evidence, and release operations visible to authorized operators.

2-second version:

Platforms: configured in data Providers: AWS live first Builds: verified before deploy Plans: review before mutation

Operator Sign In View overview

Managed platforms
Cloud provider settings
Build verification
Release operations
Plan review

1) Configure the platform
Start with a name, domain, provider account, region, and repository.
2) Review the generated plan
MerTekStak derives service names, stores, secrets, and verification settings.
3) Verify a build
Build, restore, migrate, smoke test, and record deployability evidence.
4) Promote deliberately
Deployments use verified build records and operator-reviewed operation steps.

Manage platforms from configuration.

MerTekStak treats each managed product as a database-configured platform. Similar names do not create hidden coupling: no managed platform is built in by name.

Platform records

Name, domain, provider, repository, environments, and deployment policy are explicit platform data.

Provider catalog

AWS is the first live provider; Azure and GCP are present canonically but unavailable until implemented.

Controlled setup

Operators choose from options and presets while MerTekStak derives the cloud-facing details.

Verify before production.

A build becomes deployable only after the configured pipeline produces evidence from restore, migration, smoke-test, and artifact checks.

Build watcher

Configured refs can be watched by a background job that verifies the newest useful commits.

Fresh data restore

Verification environments use selected production or source backups before migration testing.

Commit signals

Successful verification can mark commits as deployable through configured repository signals.

Operate with reviewable plans.

Setup and deployment flows create plans first. Cloud mutation is queued only after the operator confirms the generated operation.

Setup plans

Derived web, data, database, cache, artifact, health-check, and secret settings stay visible.

Deploy operations

Each deploy records steps, attempts, logs, configuration snapshots, and resulting health evidence.

Test environments

Operators can publish a selected commit to test without making that build production-deployable.

Staging environments

Staging follows the production deployment path against selected backups so migrations are exercised.

Artifact pipelines

Managed platforms can configure their own artifact outputs while MerTekStak itself remains web/data only.

Admin-only access

The interface is built for a few complete administrators, not public users or self-service customers.

Cloud-first, AWS-first.

The first working path targets AWS. Azure and GCP remain visible as canonical unavailable options so the schema does not need to be redesigned later.

AWS live path

Provider configuration, credentials, regions, and runtime resources are modeled for the first deployable implementation.

Azure unavailable

Azure is seeded as a disabled option so operators can see it is planned but not selectable.

GCP unavailable

GCP is also seeded as unavailable and can be enabled after the AWS path is complete.