Start with one outcome.

Quick start

1. Install Vaytero for Windows or open the web app.
2. Name the organization or client workspace.
3. Choose the local folder that the desktop agent may read.
4. Create an agent with a role, objective, and initial goals.
5. Keep it Read-only while reviewing its plan, or explicitly enable Free-will mode for unattended execution.

Vaya, the workspace guide

Vaya is the same expressive Vaytero companion shown on the website, in onboarding, beside assistant messages, and in the floating guide. Her working character is observant, calm, capable, gently curious, and lightly witty only when useful.

Vaya makes the experience personal by remembering workspace goals, configuration, useful preferences, and concrete progress. She avoids generic praise, emotional manipulation, dependency language, and pretending to be human. Suggestions are grounded in the current provider status, files, connectors, agent objective, and routines.

Platforms and Android support

The same product UI is shared across Windows, web/PWA, and Android. The Android APK is a universal package with no CPU-specific native libraries.

• Android 7/API 24 through Android 16/API 36.
• ARM32, ARM64, x86, and x86_64 devices supported by the system WebView.
• Responsive phone, foldable, and tablet layouts.
• Local computer actions require a paired desktop companion.

Android 6 and older are outside the supported range of the current Capacitor runtime.

Vaytero Intelligence

Customers use one managed intelligence service and do not configure model vendors, API keys, command-line runtimes, or routing. The workspace owner controls that private technical layer through a separately entitled admin console.

Credentials and routing details stay outside customer renderer state and conversation history. Relevant data subprocessors must still be disclosed through the service's privacy and legal documentation.

Permission modes

Read-only

The default for every new agent. It can inspect the assigned workspace and prepare a plan without changing files or taking external action.

Free-will mode

An explicit per-agent switch for unattended execution related to the assigned objective. The mode is visible in the agent list, top bar, profile, settings, and context rail. Operating-system protections and missing third-party authorization still apply.

Connectors

The catalog includes Gmail, Outlook, Microsoft 365, Google Calendar, Drive, Teams, Slack, Notion, HubSpot, Salesforce, Canva, files, browser, computer use, and Creator Studio. Remote services remain Setup required until OAuth succeeds and a live capability probe passes.

Credentials must remain in an encrypted broker or platform secret store. They must never be copied into conversations, browser local storage, or tenant tables.

AI Influencer Studio

Create a reusable character bible for a client business: character name, audience, expertise, personality, visual direction, voice, content pillars, platforms, campaign objective, offer, duration, and disclosure. The same profile can drive character images and repeatable video production.

Client and generated images

Productions may use original AI-generated character art, approved client photos, product images, logos, screenshots, or any combination. Vaytero stores references without overwriting source files. The user must confirm usage rights and consent before a production brief can be written.

Production bridge

The desktop app writes character-bible.json and video-brief.md under .vaytero/creator-studio/influencers/ in the selected client workspace, then prepares a task for Vaytero's private production engine.

Every brief requires identity consistency, approved claims, source provenance, disclosure, generation records, render output, and visual QA. Automatic publishing requires a separate explicitly authorized task.

Model and competitor radar

Add model providers, agent products, or competitors to a watchlist and turn it into a manual, daily, or weekly routine. Each run should prefer primary official sources, record source URLs, release dates, and the date checked, and separate verified facts from inference.

The report compares current findings against implemented Vaytero capabilities and proposes a ranked, testable improvement backlog. Vaytero does not promise to beat every competitor at all times; it creates a repeatable evidence loop for responding faster and improving where users gain real value.

Routines

Desktop routines can run manually, hourly, daily, or weekly while the companion is open. A routine inherits its agent's provider and current permission mode. Always-on cloud schedules require the hosted queue and worker described in the architecture guide.

Subscriptions and billing

Self-service Operator subscriptions use Stripe-hosted Checkout. Workspace owners and admins can manage payment methods, invoices, and cancellation through the hosted billing portal. Card details do not pass through Vaytero clients or workspace tables.

Workspace access changes only after a signed billing event is processed. The launch price shown on the website is not charged until the hosted service, authentication, live Stripe account, tax settings, and checkout endpoints are deployed.

Light, Dark, and System themes

System is the default and follows the device preference. Light and Dark can be selected from the top bar. Both retain the Vaytero indigo/coral identity, readable contrast, warm neutrals, clear focus states, and reduced-motion support.

Workspace roles

The SaaS schema supports owner, admin, member, and viewer. The person who creates a hosted workspace becomes its owner. Local-only onboarding does not create an online account or silently assign an email address.

Deployment boundaries

The local clients, production web build, database schema, and download site are buildable now. A public paid service still requires deployment targets, domain access, secure connection applications, encrypted secrets, billing credentials, monitoring, code-signing certificates, and Apple release infrastructure.