AI model deployment
How to use
Baseten.
Turning open or custom models into versioned autoscaling APIs with development deployments, stable environments, observability, and controlled promotion.
Baseten is a managed platform for packaging, deploying, scaling, and operating AI models. Turning open or custom models into versioned autoscaling APIs with development deployments, stable environments, observability, and controlled promotion. This guide covers the whole path in one place: official access, a first session that produces something reviewable, the checks that make output trustworthy, and the permissions worth limiting before you connect real work.
AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.
Access & setup
Find, install, and sign in to Baseten
Get into the official Baseten experience with the right account and a setup you understand.
- 01
Start at https://www.baseten.co/ and confirm the domain before entering account or payment information.
- 02
Availability: Baseten is accessed through its web dashboard, inference and management APIs, and Truss command-line tooling.
- 03
A Baseten account and API key, network access, a supported Python environment for Truss, and model artifacts with suitable licenses and hardware requirements.
- 04
Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.
- 05
Run one low-risk test task before connecting sensitive files, repositories, or workspace data.
- Use official download pages.
- Review permissions during setup.
- Keep installers and applications updated.
First session
Your first useful Baseten session
Learn the interaction loop using a small task with a clear outcome.
- 01
Define the model, license, endpoint schema, secrets, dependencies, GPU requirement, and acceptance tests.
- 02
Create a reproducible Truss configuration and push an isolated development deployment.
- 03
Inspect build and load logs, then test quality, errors, concurrency, latency, and resource use.
- 04
Publish and promote only after staging evaluation, retaining the previous deployment for immediate rollback.
- State the outcome before the background.
- Provide the real source material.
- Review the result before expanding the task.
Quality control
Check the quality of Baseten output
Establish that a change is safe to run in production and reversible if it is not.
- 01
Restate the intended end state and the blast radius before applying anything.
- 02
Review the generated configuration line by line against the provider's current documentation.
- 03
Apply to a non-production environment first and confirm the observed result matches the intended one.
- 04
Confirm the rollback path works by actually exercising it, not by assuming it exists.
- 05
Check cost, scaling limits, and network exposure before the change reaches production traffic.
- Test the rollback, do not assume it.
- Check what a configuration exposes to the public internet.
- Watch cost and rate limits as closely as correctness.
Privacy & permissions
Use Baseten safely
Keep credentials, network exposure, and cost under deliberate control.
- 01
Use scoped, short-lived credentials, and never paste production secrets into a prompt or config file.
- 02
Confirm what each change exposes publicly before applying it, especially storage, databases, and admin endpoints.
- 03
Separate environments so a mistake in development cannot reach production data.
- 04
Set billing alerts and hard quotas before enabling autoscaling or usage-based services.
- 05
Review audit logs and revoke access for integrations that are no longer in use.
- GPU deployments can create ongoing cost and production logs or traces may contain sensitive data. Use secret references, environment separation, bounded autoscaling, output validation, access controls, and reversible promotions.
- Follow your organisation's approved-use policy.
- Never treat fluent output as authorization to act.
Core workflows
Step-by-step ways to use Baseten for the work it does best.
Each workflow is a separate guide with its own steps and review checkpoints.
Move a model from a reproducible Truss configuration into an isolated development deployment.
↗ 02 WorkflowPromote and operate a Baseten production environmentUse stable environments, autoscaling, monitoring, and reversible promotion for a controlled model release.
↗Official references
Check the current product documentation.
Features, plan limits, availability, and data controls change. These official pages are the starting points used for this guide.