Does Octri generate C# or a Terraform provider?

Not today, and the importer names any language it skips. Octri generates SDKs in TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart.

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 liblab to Octri

Upload liblab.config.json with the spec it points at. Your spec, languages, auth schemes and package name come across, and the rest is a few settings in SDK Studio.

Start on the Free plan Book a call

Written by Octri · Checked 25 October 2026

What to have to hand

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

liblab.config.json
openapi.json

What comes across

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

What	In Octri	From liblab
Spec	The project’s spec	specFilePath or specUrl
SDK languages	One SDK per language	languages
Auth schemes	SDK auth settings	auth
Package name	SDK package name	The first name in languageOptions
Project name	Project name	apiName or sdkName
Retries, pagination, environments	Set in SDK Studio	By hand
Hooks	Moved as code into the SDK repository	By hand

Step by step

Bring it in
Sign up, choose Switch to Octri when onboarding asks for your spec, and drop in liblab.config.json with the spec it names, or a .zip of the repository that holds both.
Check the preview
Before anything is created, Octri shows what it found: the spec, each language, your auth schemes and the package name. Anything it could not carry is named in a note under the preview, so you know what is left to do by hand.
Fill in the SDK settings
Set environments, retries and pagination in SDK Studio, and check each language’s package name. Hooks are code, so they move into the SDK repository, where custom code is kept through each regeneration by a normal merge.
Set up your SDKs
Generate each language and compare it with the package you ship today in the SDK Studio preview. Give each language the package name your users already install, and publish the first Octri release as a new major version, since method names and types can change. Every later spec change arrives in the SDK repository as a pull request.
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

Octri writes and hosts the docs from the same spec, with the call through your SDK on every endpoint page. If the written pages live on Mintlify or ReadMe today, their guides here cover moving those as well.