Marketing Automation Platform
Marketron
An autonomous digital marketing operating system for planning, producing, approving, and publishing multi-brand campaigns.
Overview
Marketron is an autonomous digital marketing operating system for multi-brand marketing operations. It connects planning, content production, approval, channel publishing, and analytics in one governed workflow.
The platform is built around a domain model for brands, campaigns, content, assets, approvals, channel adapters, and analytics, with an agent-assisted planning and supervision layer.
Origin and motivation
Marketing operations across multiple brands accumulate fragmented briefs, assets, approvals, channel-specific requirements, and performance context. The platform direction is to make that work observable and repeatable.
The problem
Teams need a durable record of what was planned, produced, approved, and published, with brand context and governance applied consistently across channels.
Who it is for
Multi-brand marketing teams, agencies, and operators who need a governed production workflow rather than a collection of disconnected scheduling tools.
Vision and objectives
A planning and production system where agent assistance is bounded by explicit approvals, channel adapters, and an auditable workflow.
Key capabilities
- Planning DAG and campaign objectives
- Server supervisor loop and agent runs
- Brand kits, content drafts, and asset management
- Approval workflows and governance
- Telegram and mock channel adapters
- Analytics and performance context
- MCP read and write tools for controlled integration
Engineering and architecture
Marketron uses Django 5.2 LTS and Django REST Framework, PostgreSQL, Redis, Celery, HTMX, Django Unfold, and an MCP server. The repository describes 105 canonical models across 12 domain applications.
The project is an internal beta. Live AI provider calls remain blocked in the current evidence, and no public commercial launch is claimed.
Difficult problems and solutions
Governed autonomy
Agent-assisted planning must remain inside approval and publishing boundaries. The workflow records who approved what and which channel adapter received it.
Channel-specific publishing
Each channel imposes its own content, scheduling, and credential model. Adapters isolate those differences from the core campaign workflow.
Evidence limits
The current acceptance evidence covers a remote internal deployment and health checks, not a public production launch or verified AI output quality.
Current status
Marketron is a beta internal deployment. The acceptance record documents a remote deployment to a private server and a successful health check. The phase status still records no public production deployment, and live AI provider execution is blocked.
No public product URL, customer adoption, or revenue figure is claimed. Enterprise inquiries can be directed to Simorgh.
Discuss Marketron
If this work is relevant to your organization, start with the problem and the context.