# Growth Infrastructure for Developers | MarkenGroup Cloud

Last reviewed: 30 August 2026

[HTML](https://markengroup.cloud/) · [Documentation](https://docs.markengroup.cloud/)

Shared growth infrastructure that keeps teams, projects and activation products in one governed control layer.

## Current status

The shared Cloud workspace is live. Product capabilities vary: TrackMailer has a live workspace foundation, TrackAny.Click is a local release candidate awaiting production deployment, and TrackPost is coming soon.

## Your tools see channels. Your business needs the journey.

A click dashboard, an email sender and a social scheduler can each look healthy while nobody can explain which touchpoint produced a signup, purchase or return visit.

- **Context gets lost:** Campaign IDs, project ownership and conversion definitions drift when every tool carries its own model.
- **Control gets duplicated:** Separate accounts, team access and credentials create more places for permissions and secrets to go wrong.
- **Activity replaces outcomes:** Clicks, opens and reach become the answer because the journey to conversion was never connected.

## Activation creates the touchpoint. Attribution explains the outcome.

TrackMailer is the email activation layer. TrackAny.Click is the first-party data and attribution layer. TrackPost is the planned social activation layer. The shared Cloud context keeps the boundaries explicit.

- **TrackMailer — Email activation:** Prepare recipients, sender identity and message intent. Customer delivery and delivery events are not active yet.
- **TrackAny.Click — First-party attribution:** Preserve campaign, session, event and outcome context. The collector and Ads mirror are prepared locally but not deployed or provider-accepted.
- **TrackPost — Social activation:** Planned publishing will carry measurable campaign context into the same journey.

## Your coding agent should read the contract—not invent the infrastructure.

Stable terms, crawlable status pages and copyable contracts give Codex, ChatGPT, Claude and other coding agents a factual source of truth. When a public endpoint does not exist, the docs say so.

- `Add email infrastructure to this Firebase project.` — Start from the sender, audience and Sandbox contracts without exposing a server secret in React.
- `Design attribution for every signup source.` — Define campaign IDs, sessions and conversion events before wiring a collector.
- `Explain which product is ready today.` — Read explicit Available, Sandbox, Preview and Coming soon states from the same public source.

## Shared context without shared access.

- **One identity:** A person uses one Firebase Auth identity across the Cloud Services family.
- **Organizations and projects:** Teams group work by organization and keep each website, shop or brand in the project that owns its data.
- **Explicit permissions:** Active membership, project context, product entitlement and server-side permissions are checked separately.
- **Separated product data:** Shared IDs connect context; they do not grant one product direct access to another product's private data.

## Infrastructure earns trust by showing its boundaries.

There are no invented compliance badges or vague security claims here—only mechanisms that exist in the current architecture.

- **Verified identity:** Core operations require a verified email address and active organization membership.
- **Project-scoped access:** Product reads and writes are checked against the selected project and entitlement on the server.
- **No customer-domain Firebase writes:** Customer websites use product ingress boundaries; they never write product events directly to Firebase.
- **Secrets stay server-side:** Private credentials are not placed in VITE_* configuration, browser examples or public documentation.

## Know the boundary before you build.

### What is MarkenGroup Cloud?

It is the shared control layer for organizations, projects, teams and the TrackMailer, TrackAny.Click and TrackPost product family. Each product keeps its own data and availability.
### Are all three products available?

No. The Cloud workspace is live. TrackMailer has a live workspace and audience foundation without customer delivery, TrackAny.Click is a local release candidate with no public collector deployment, and TrackPost is coming soon.
### Can I use the platform with React, Firebase or an AI coding agent?

Yes for the documented platform and preview workflows. Use the public docs as the source of truth and do not let an agent guess endpoints, credentials or unavailable capabilities.