Node.js SDK

The openship package gives your application access to projects, deployments, domains, backups, and the other platform operations. Native SDK calls and HTTP controllers use the same shared core.

Choose a mode

Mode	Use when	Start here
Remote client	Openship already runs on a server or in Cloud.	Connect to an API
Native SDK	Your Node application owns storage, providers, and the installation lifecycle.	Embed Openship

Both modes expose the same named operation groups. A configured provider and the caller's permissions determine which operations can run.

Install

The SDK is currently a repository preview. Published [email protected] contains the CLI only. Build and install the SDK tarball before using these imports.

A deployment in code

This function accepts either a remote client or a native user scope:

deploy-site.mts

import type { OpenshipClient, ScopedShip } from "openship";

export async function deploySite(ship: OpenshipClient | ScopedShip) {
  const submitted = await ship.deploy({
    name: "my-site",
    source: { type: "files", files: { "index.html": "<h1>Hello from Openship</h1>" } },
  });
  const outcome = await ship.deployment(submitted.deployment_id).wait({ timeoutMs: 120_000 });
  if (!outcome.success) throw new Error(outcome.message ?? outcome.status);
  return ship.projects.get(submitted.project_id);
}

Next steps

Deployment workflows

Deploy files, directories, or Git sources; follow logs and handle decisions.

Users and organizations

Select a tenant and connect your application's verified identities.

Runnable example

Deploy, redeploy, reopen state, and clean up using the installed package.

Method reference

Find every current operation, organized by resource.