liveBook · Manning

Vendor lock-in

As explained in Vibe Engineering

Vendor lock-in is dependency on a particular supplier that makes switching to an alternative costly or difficult.

Vendor lock-in is dependence on a supplier that makes switching costly or difficult. In AI applications, direct provider integration can bind application behavior, credentials, and deployment assumptions to one API. Encapsulating provider access keeps the infrastructure decoupled and makes substitution a practical engineering requirement rather than a late migration project. section 6.0

Treat provider flexibility as an explicit tradeoff:

  • Use a provider boundary so application code can select different AI providers through configuration rather than provider-specific changes throughout the system. section 6.4.6
  • Recognize that managed gateways simplify switching and compliance, but may create lock-in to a wider cloud ecosystem and delay access to newly released models. section 6.0
  • Validate equivalent behavior after migration instead of treating a successful deployment as proof that providers are interchangeable. section 6.0 section 6.5

Switching from Gemini to OpenAI

A deployed SQL-generation service changes its active provider by setting AI_PROVIDER=openai and referencing an OpenAI secret. The service restarts, initializes the OpenAI client, and serves traffic without rewriting application logic. section 6.4.6

Listing 6.27 Switch the AI providers
gcloud run services update sql-generator-service \
--set-env-vars=AI_PROVIDER=openai \
--set-secrets=OPENAI_API_KEY=openai-api-key:latest

Inspect the deployment command that changes the active provider and supplies the provider-specific secret. section 6.4.6

How Vibe Engineering covers it

How deep it goes
Demonstrates provider substitution operationally, but stops short of a broad economic analysis of switching costs.
Examples
Uses Gemini and OpenAI switching, Cloud Run updates, provider logs, API keys, and generated SQL validation.
What it assumes
Assumes familiarity with APIs, deployment configuration, environment variables, secrets, and basic integration testing.
What you can do after
Operate/configure a deployed service to switch AI providers while preserving application logic and checking runtime initialization.
How it connects
Connects provider abstraction with cloud deployment, configuration management, secret management, model accuracy, and integration testing.

Also explained in

Compare how 8 books explain vendor lock-in →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.