Home/Platform/Self-hosted AI agent for marketing

Weekly marketing that runs on your machine

Tin is a self-hosted AI agent for marketing, built as an open-source system for coding agents. Our team sets Tin up inside your environment, on your repo and your data, and runs the weekly jobs. The code is open, so your team can also run the system itself.

Book a call

Run marketing from a coding agent
System
Tin's System view: scheduled and available workflows for a project

What is a self-hosted AI agent?

A self-hosted AI agent runs on a machine your team controls. Your team manages the installation and the files its jobs use. For marketing, those files can hold research, drafts and reports, giving the next audit or writing job earlier work to read.

Tin is an MCP server for Claude Code, Codex or Cursor. The coding agent calls a workflow; Tin handles its timers, retries and wait for review. You can run that system with your own keys, data and schedule. With a vendor-hosted service, the installation runs on the provider's infrastructure.

An agent built from prompts costs your engineers constant tuning

Getting a draft from a prompt is only the start of a recurring job. Someone has to arrange the next run, give it the right context and keep its instructions useful.

  • Jobs need restarting. An engineer returns to the prompt when the next report or draft is due.
  • Context needs rebuilding. A later run needs a record of earlier research and decisions to continue the work.
  • Instructions need tuning. The team keeps adjusting the job to make its output useful on the next run.

Tin supplies schedules, project memory and review for the jobs that need to keep running.

You hold the keys, the data and the schedule

Run the system on your machine and keep the research, drafts and recurring jobs in a project your team can inspect.

Keep your own keys

Use your own keys when you run the system yourself. Tin connects the coding agent to marketing jobs while the installation stays on the machine your team controls. Manage the recurring jobs there, with their inputs and schedules available to inspect.

Keep the project on a local machine
Files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Read the project files

Reports, research, drafts and the project wiki live as plain files in a git repository. Open the files to read what a job produced, and use the history to follow changes. The next person working on the project can inspect the same material.

Read reports and drafts with history
Files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Set the recurring jobs

Workflows save their inputs and schedule, so the weekly job has a defined starting point. Tin handles the timers and retries around each run. The week view puts the recurring work in front of the team, from research and writing through review and measurement.

See the recurring marketing jobs
Week view
A week of a growth system in Tin: research, writing, checks, paid ads, email, review and measurement, day by day

Review the draft

Drafts arrive as a pull request or a one-click publish. Nothing goes out on its own. The decision card holds the next action, including publishing, opening a pull request or leaving the draft for later. A GitHub change is ready for the owner to inspect and merge.

Carry context into later runs

A later run can read the project's earlier work through project memory. Company research and decisions stay alongside the reports and drafts. The coding agent uses that context to fill the next job's inputs and review what it produces.

Carry project context forward
Files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Tin's workflows cover search, content, outreach, ads and measurement

Research search opportunities

Run audits and keyword plans to identify the buyer questions your pages should answer. See workflows

Prepare article drafts

Produce drafts in the owner's voice and refresh existing pages from the project context. See workflows

Draft social posts

Prepare X and LinkedIn drafts for review from the ideas and material in the project. See workflows

Run paced outreach

Build a mailbox shortlist and run an email campaign with follow-up that stops on replies. See workflows

Assess paid search

Examine whether Google Search ads fit the business, then use campaign check-ups to review the work. See workflows

Read the response

Bring a weekly brief and PostHog analytics brief into the project for the next decision. See workflows

  • Claude Code
  • Codex
  • Cursor
  • GitHub
  • Google Search Console
  • Google Ads
  • Stripe
  • PostHog

Start with one repository, connected by one command

The hosted connection works with your marketing-site repository. The same projects are available in the browser.

Connect the hosted project
System
Tin's System view: scheduled and available workflows for a project

Connect the hosted server

Add Tin to Codex with the command below, or open the same projects in the browser.

Try in browser →

codex mcp add tin --url https://app.tin.computer/mcp
Start with the marketing site
Files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Begin with one repository

Connect the outward-facing marketing site first, so your first jobs work with the pages buyers see.

Self-hosting is possible

The whole system can also run on your team's own machine from the repository.

Open the repo →

Every workflow is open source you can read and change

Read the code

Each workflow is a folder containing its steps, data inputs and evaluations.

Change a workflow

Edit its files to adapt the job your coding agent runs.

Bring your own skills

Turn skills into workflows with the system's one-command conversion.

Keep the source

Open source, Apache 2.0.

Talk to Tin

We set Tin up inside your environment, on your repo and your data, and adapt the workflows to the way your team already works. Our people run the weekly jobs and improve the workflows. The code stays yours after we leave.

Book a call

FAQ

Can it replace a marketer?

People still decide which marketing jobs to run and whether the work is useful. A technical team can operate and change the system themselves. If you want help setting it up and improving the workflows, Tin's service supplies people to do that work with your team.

What is an MCP server?

An MCP server makes tools available to a coding agent. Through Tin's server, Claude Code, Codex or Cursor can call marketing workflows while working with your repository. The command on this page connects Codex to the hosted server; it does not install Tin on your machine.

Whose model keys does the agent use?

Self-hosting uses your keys and your choice of coding agent: Claude Code, Codex or Cursor. Your team manages both the agent and the Tin installation. The marketing jobs use the project files and schedules you keep in that installation.

Does self-hosting cost anything?

You can run the Apache 2.0 code without paying Tin for it. Your team supplies the keys and machine and spends time running the system. Tin's team can do that work for you, from setup to the weekly marketing jobs.

Hand your weekly marketing jobs to Tin's team

Talk with the founders and engineers who set Tin up and run the work. We can discuss which weekly marketing jobs to start with and how we would run them in your environment.

Book a call