How this works in FrescoAds
Use the system as one operating record
FrescoAds uses managed model access on its published plans and can route supported image, video, language and audio work across providers enabled for the customer deployment. Provider names shown on the public site describe configurable integration families; they do not mean every model is active for every workspace.
- FrescoAds-managed model access
- Workspace provider sets
- Task-level route selection
- Visible provider and output lineage
Classify the production task
Choose the job before choosing the provider: concept image, product edit, short-form video, language development, localization, voice or audio production, or review assistance.
Define the expected input and output, fidelity requirement, controllability and whether the task is exploration or production. One campaign may use different providers for different jobs while returning all outputs to the same record.
Check before continuing
- Input and output type
- Required control and fidelity
- Exploration or production use
- Human decision required after output
Start with the enabled provider set
Use only providers enabled for the workspace and task. The active set is determined by the customer deployment, FrescoAds availability and applicable commercial and data-processing terms.
Published Essential and Regional plans use FrescoAds-managed access. Customer-approved provider arrangements are assessed for Enterprise deployments only when the technical, commercial and legal route is available.
Check before continuing
- Provider is active for the workspace
- Capability matches the task
- Commercial route is understood
- No unsupported provider is presented as available
Apply data and rights policy
Consider what will be sent to the model: prompt, source image, product material, script or other selected content. Do not use a route that is not approved for the relevant data class or rights requirement.
Provider retention, training and usage terms can differ. Deployment documents and the active sub-processor information govern production use, not the public logo rail alone.
Check before continuing
- Permitted data class
- Approved source rights
- Provider terms reviewed where required
- Restricted data is excluded
Compare representative outputs
Evaluate providers using the same brief, source and review rubric. Consider product truth, strategic fit, temporal or visual consistency, revision effort, latency and credit usage.
The lowest-cost generation is not necessarily the lowest-cost production route. Record whether an output can be controlled and finished to the required standard.
Check before continuing
- Common evaluation context
- Quality and controllability reviewed
- Revision effort considered
- Credit use is visible before execution
Set a primary and fallback route
Select the route that best fits the production job and record the reason. When continuity matters, define a pre-approved fallback with its own limitations rather than allowing users to select any available model.
A fallback preserves operational continuity; it does not guarantee identical outputs or provider availability.
Check before continuing
- Selection rationale recorded
- Fallback route approved where needed
- Provider-specific limitations noted
- Responsible administrator identified
Keep the model decision with the campaign
Attach provider, prompt or instruction context, selected sources, outputs and later edits to the campaign route. Reviewers should be able to understand where the current version came from without reconstructing a separate tool history.
FrescoAds provides the operating record and routing controls. Customers still review outputs for accuracy, rights, claims, brand fit and market suitability before use.
Check before continuing
- Current provider and output are traceable
- Sources and edits remain connected
- Human review state is visible
- Usage context can be explained
Common questions
Clarify the operating boundary
No. They represent provider families FrescoAds can be configured to support. Actual availability depends on the customer deployment, capability, region and provider agreement.