Do I get a docs site as well?

Yes, from the same spec. Every endpoint gets a page with the call through your new SDKs in each language you publish, on your own domain, on every plan.

Does trying the import change my current setup?

No. The importer only reads the files you upload, and Pull from GitHub only reads your repository. Nothing is written back to either, so your current site keeps running until you move the domain.

Will someone help with the move?

Yes. Book a call and a founder will go through your project with you and help the first release over by hand. Questions also reach us at founders@octri.dev.

Migration guide

Migrate from Stainless to Octri

Upload stainless.yml with the OpenAPI file beside it. Your targets, package name, production repository and method names come across, and your users keep installing the packages they already have.

Start on the Free plan Book a call

Written by Octri · Checked 25 October 2026

What to have to hand

Octri reads Stainless’s own files. A .zip of your repository or a single config file, up to 15 MB.

stainless.yml
openapi.yml

What comes across

Each row is a field the Stainless importer reads, and where it lands. Rows marked “By hand” are what is left for you.

What	In Octri	From Stainless
SDK languages	One SDK per target	targets
Package name	SDK package name	package_name of the first target
Repository	The SDK repository	production_repo
Project name	Project name	organization.name
Method grouping	Methods grouped by tag	resources
Method names	Per-endpoint names	x-stainless-method-name in your spec
Names inside resources	Set in SDK Studio	By hand

Step by step

Bring it in
Sign up, choose Switch to Octri when onboarding asks for your spec, and drop in stainless.yml with your OpenAPI file, or a .zip of the repository that holds both.
Check the preview
Before anything is created, Octri shows what it found: the spec, each target as an SDK language, the package name, the repository, and which methods carry a name from your spec. Anything it could not carry is named in a note under the preview, so you know what is left to do by hand.
Check the surface
Method names set under resources are not read, so set those in SDK Studio, where the preview shows each call as your users will write it. Compare it with the package you ship today before the first release.
Release one language first
Release one language under its existing package name as a new major version, then add the rest one at a time. Each regeneration after that opens a pull request in that language’s repository.
Go live
Publish, then point your custom domain at Octri last, so readers keep the old site until the new one is ready. From then on every merged spec change rebuilds the draft of your docs, SDKs and MCP tools, ready for you to publish.

Questions

The importer skips them and names each one in the preview. Octri generates SDKs in TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart.