API Support Overview

• Targeting a Deployment Environment

The following table shows the status of the interfaces Spin provides to applications.

For more information about what is possible in the programming language of your choice, please see our Language Support Overview.

Targeting a Deployment Environment

Some Spin runtimes may support a different set of APIs from those listed above, or may support only older versions. For example, some runtimes might not support SQLite, or Serverless AI; or the Spin 3.2 runtime does not support the most recent PostgreSQL API introduced in Spin 3.4. This is an important consideration when writing a Spin application that will run in a different environment from your development environment: you do not want to depend on SQLite if you will have to deploy to an environment without it.

You can tell the Spin CLI about the environment (or environments) that you plan to deploy into using the application.targets field in spin.toml. If you do this, spin build verifies the set of APIs used by your components against each listed environment. If a component uses APIs that wouldn’t be supported, spin build will warn you.

For example, here is how to specify that you want your application to be compatible with spin up version 3.2:

# spin.toml

[application]
targets = ["spin-up:3.2"]

For the other runtime environments such as SpinKube or commercial clouds, see the documentation for those projects for their environment IDs.