You are buying an execution system for your operators, not an outsourced media team. Start with one recurring task and an accountable implementation owner.
For a channel lead, marketing engineer or Head of Performance who needs a repeatable workflow inside accounts the business already controls.
Bring a recurring account task, an operator who can configure the tools, and a sponsor who can approve the rollout.
See a demo for your in-house team →For an agency owner or operations lead standardizing how media buyers research, prepare, review and deliver work across authorized client accounts.
Keep each client’s configuration and material separate. One operator prepares the package; an authorized reviewer decides what goes to the account.
See a demo for your agency →You need someone to manage the account for you, expect a prompt pack with no setup, need guaranteed performance, or require verified enterprise features such as SSO or an SLA. Multi-entity portfolios and new conversion models need a fit review rather than assumed coverage.
Explore managed execution instead →A map of the self-hosted workflow. Your team supplies the facts, configures the connections and keeps authority over production actions.
Product facts, approved claims, account context and research sources.
Inputs you supplyInspect the source, work product, target account, budget and required approval.
Operator decisionThen, the authorized account action. Preparation, provider rendering, publishing and campaign execution remain distinct steps. Read back what actually changed.
Configured reporting can inform the next research question. The observation still needs its source, period and limits.
Your configured machine and providers. Your operator runs the documented workflow. License cost is one-time; provider usage, hosting and ad spend are separate.
A narrower hosted workflow with purchase-bound access and wallet-based usage. It is a separate interface, not a browser version of every repository capability.
Inspect the kinds of records your operators prepare, the decision each one supports and the limit to keep in view. These are workflow descriptions, not completed customer artifacts.
Choose a stage to explore its deliverables. Counts describe the representative records below.
0–10 · representative records, not performance or total product coverage
10 of 10 workflow records. Open a title to inspect the next action and boundary.
| Work product | What the package contains |
|---|---|
Research and evidence | 2 shown |
An account findingWhat your reviewer checks Which account, source and period support the observation? Next actionDecide whether more evidence or a scoped change is useful. Keep this boundaryA read-only audit is not an applied account change. | A checked finding, evidence and next useful check. |
A market and audience briefWhat your reviewer checks Check the market, approved claims and sources before accepting the direction. Next actionUse the brief in the selected campaign, page or creative workflow. Keep this boundaryResearch context does not establish demand or grant account access. | Product facts, audience context and source-backed research for the chosen account task. |
Packages and production | 6 shown |
A Search campaign packageWhat your reviewer checks Check claims, destinations, economics and the intended account. Next actionReview the package before the guarded upload step. Keep this boundaryA prepared file is not a live campaign or demonstrated performance. | Ad-group structure, exact keywords, responsive search ads and validation findings. |
A feed and Shopping planWhat your reviewer checks Review actual product inputs, Merchant Center requirements and account permissions. Next actionUse the documented deployment path only for approved work. Keep this boundaryRequires your configured store, feed and advertising connections. | Feed segmentation, rewrite work and Shopping campaign preparation. |
A PMax asset packageWhat your reviewer checks Check feed context, destinations, asset suitability and the intended account. Next actionReview the package before a documented account action. Keep this boundaryPrepared assets are not a live PMax campaign or an observed performance result. | Asset-group preparation, copy and creative inputs for the selected PMax workflow. |
A Demand Gen packageWhat your reviewer checks Review audience assumptions, assets, account permissions and budget. Next actionApprove the specific package before the guarded execution step. Keep this boundaryYour configured connections and account eligibility determine usable scope. | Campaign and creative preparation for the documented Demand Gen lane. |
A presell or offer pageWhat your reviewer checks Check source-backed claims, mobile behavior, destination and review findings. Next actionApprove the page before a documented deployment. Keep this boundaryPublishing and paid traffic are separate authorized actions. | Research, copy, build and review artifacts for the selected page. |
A static or video production briefWhat your reviewer checks Check brand facts, claim support, format and provider cost before production. Next actionAuthorize the selected rendering or production step with its budget. Keep this boundaryA brief is not a rendered asset; model and rendering usage is separate. | Copy, visual direction and production inputs for the enabled creative workflow. |
Review and account decisions | 2 shown |
A launch decisionWhat your reviewer checks Confirm scope, budget, permissions and launch-readiness evidence. Next actionAn authorized operator applies the change and reads it back. Keep this boundaryNo account is connected or changed by this example. | A validated change package and the findings that can block it. |
A reporting readWhat your reviewer checks Separate preparation, actual execution and observed results. Next actionUse the supported finding to choose the next check or brief. Keep this boundaryConfigured source access is required; a report is not a guaranteed result. | Account evidence with a named source, period and interpretation. |
Source: Current published product scope · A selection of supported work, not a complete inventory, live execution log or customer result.
A Search campaign package your media buyer can inspect before upload. This is an illustrative walkthrough of a supported workflow, not a live run or a customer result.
A media buyer defines the product, market, approved claims and destination. This example uses an invented footwear brief, not a client account.
Name the product, market, approved facts, sources and the work you want prepared.
Example data · no client account · nothing sent
EXAMPLE BRIEFTask: prepare a Search campaignProduct: everyday trail footwearMarket: one approved regionInputs: product facts + keyword evidenceOutput requested: reviewable campaign packageIllustrative work product · no connected account or paid production
Blueprints, private source and matching web-agent access together. One full edition for the people who will operate it.
Full Agentic System · internal business/team use
Final sale · applicable tax shown at checkout. Lifetime repository updates. Provider costs, hosting, ad spend and hosted-agent usage are separate. Installation and managed execution are not included.
Allow 2–3 days for installation and account configuration; rollout depends on your integrations. This is a planning allowance, not an installation or performance guarantee. Permissions and external approvals can take longer.
| Surface | Access and cost boundary |
|---|---|
Licensed source Included | Private repository, blueprints, documentation/templates and lifetime repository updates. Your team installs and operates the workspace. |
Matching web agent Access included | A focused hosted interface for the named purchaser. Wallet-based usage is separate; this is not the full repository in a browser. |
Production connections Separate | Your authorized provider accounts, model/rendering usage, data services, hosting and ad spend. Enable only the workflows you configure. |
Managed execution Separate engagement | Installation, account operation and paid consulting are not bundled managed services. Choose a separate service path when Tegra should own delivery. |
Name the person who will install, configure and review the team's work.
Use the documented runtime versions for the workflows you enable.
Bring the permissions for the account and measurement work your team wants to run.
Connect the store, feed and creative providers you actually need, with their usage costs budgeted.
Current edition boundary. Install and authorize the integrations you actually use. A workflow existing in the repository does not give it access to your accounts or permission to spend.
The purchasing business can use the licensed system internally, including agency work on authorized client accounts. The license does not permit resale or shared logins. Keep an accountable operator and a separate reviewer. This is a suggested rollout sequence, not a live progress tracker.
The named purchaser receives dashboard access and repository delivery. Accept the GitHub invitation with an individual account. Never circulate a Tegra password, GitHub login or provider token.
Your authorized team works in a controlled private business workspace. Keep client folders, account permissions and credentials separate. Additional direct Tegra or vendor-repository access needs a named entitlement review; colleagues are not automatically granted access.
Prepare a read-only account audit: record one checked finding, its evidence and the next useful check.
A second operator should be able to follow the sources, inspect the output and name the next authorized step. Provider production, publishing and account changes still need their exact permissions and budgets.
Keep the source version, actual artifact and review findings. A useful first workflow informs expansion to another approved account; buying the product does not enroll a team, connect an ad account or authorize a launch.
Source: Native first-task contract and internal-team access terms · Upcoming means a proposed step, not enrollment, attendance or verified activation.
Lifetime repository updates are included under the current purchase terms. Improvements from the internal systems are reviewed and released to the productized buyer repositories. An internal commit is not a delivered update, and the licensed edition is not a promise of full internal-system parity.
Use the changes and update notes available in your authorized buyer repository. Retain the version and review the scope; an internal commit is not proof of latest buyer delivery.
Follow the documented git pull and setup/update guidance, preserve local configuration and credentials, and review compatibility before applying changes.
Keep the actual artifact and readback before expanding use. No fixed release cadence, free implementation, automatic colleague access or lifetime SLA is added.
Paid training and consultation are optional, independently useful services. Google Ads and Meta Ads sessions are USD 1,500 for 90 minutes; the two-hour Agentic AI session with both founders is USD 3,000. Agree one question, prepare permitted inputs and keep the actual session artifacts. These are separate from free discovery, a product demo and done-for-you execution.
A product demonstration focuses on your team’s first workflow, its review decisions, setup and running costs. It is distinct from a paid consultation or a managed-service engagement.
Explore a Google system demo →The Tegra web agent lets you explore its supported browser workflow. It is not a live demonstration of every capability in the private repository, and trial/paid usage follows the agent’s displayed terms.
Open the matching agent preview →Read the forwardable buyer brief → Includes the offer, operator responsibilities, costs and access boundaries.
The full agentic edition is $19,997 USD. It includes the licensed private source repository, blueprints and curriculum, the included templates/documentation, matching Tegra web-agent access and lifetime repository updates. It is not a managed account service.
No. Your model/provider accounts, rendering, research/data services, hosting and ad spend have separate costs. The matching Tegra web agent uses wallet-based billing. Access is included; unlimited hosted runs and prepaid credits are not. Use the costs displayed by each provider and start with a bounded workflow.
Yes, the purchasing business can use the licensed source internally through authorized team members, including work on client accounts the agency may manage. Use separate named logins and a controlled private workspace. Additional direct Tegra or vendor-repository access needs a named entitlement review. There is no shared-login, automatic colleague access or resale right.
Allow 2–3 days for installation and account configuration; rollout depends on your integrations. A technical operator comfortable with a terminal and Claude Code. macOS, Python 3.12+ and Node.js 20+. Your Google Ads permissions and Google Cloud configuration. Shopify, Merchant Center and research/creative provider accounts for the workflows you enable. This allowance depends on your operator and external permissions; it is not an instant-setup guarantee.
Install and authorize the integrations you actually use. A workflow existing in the repository does not give it access to your accounts or permission to spend.
Its original documentation, materials and payment history remain available through the existing dashboard. It does not automatically become the full system. Any available paid upgrade must be explicitly reviewed from the purchaser’s authenticated dashboard; the standalone Blueprint edition is no longer sold.
The preview is a narrower hosted-agent workflow with its own trial and usage limits. A product demonstration explains the retained repository, one representative workflow, review decisions, team adoption and operating costs. A fixed example on this page is illustrative; it is not live telemetry, a client result or a paid model run.
Repository updates and documentation are included. For delivery or access problems contact hello@tegra.co. Installation, operational consulting and ongoing account management are separate engagements; no support response-time SLA is included. Digital-product sales are final under the published terms; review the scope before buying.
Google Ads AI Agentic System. One full edition, $19,997 once. Review the included access, setup and costs before purchase.
Review the full edition →Already bought Blueprint? Your original dashboard materials and purchase history stay available. It does not automatically become the full system. Open your existing access.