Build your backend
without the busywork.

1. Create an account and project.Open the Nodvian dashboard, choose Developer, then name your workspace and project.
2. Create a table.Open Database → Tables. Create a table named tasks with title and status columns.
3. Create an API key.Open Settings → API keys. Choose the smallest permission your app needs and restrict the key to your production domain.
4. Call the API.Store the key in an environment variable, never directly in browser source.

const NODVIAN_URL = "https://nodvian.cloud";
const NODVIAN_KEY = process.env.NODVIAN_API_KEY;

const response = await fetch(`https://nodvian.cloud/api/v1/tasks`, {
  headers: { Authorization: `Bearer ${NODVIAN_KEY}` }
});

const { data } = await response.json();
console.log(data);

A Nodvian account contains one workspace and project in the current release. Your project owns its tables, application users, API keys, stored objects, functions, realtime events, and logs.

Create keys in Settings → API keys. The complete key is shown once. Store it in a server-side secret such as NODVIAN_API_KEY.

Tables use PostgreSQL. A table name or column must begin with a letter or underscore and may contain letters, numbers, and underscores. New tables automatically receive id, created_at, and updated_at fields.

Create and inspect tables visually, add rows, or run validated SQL from the dashboard SQL editor. API responses return { "data": ... }.

Nodvian can manage the users of your application separately from your Nodvian dashboard account. Signup and login use the project API key. Successful authentication returns an ndv_user_… access token valid for 30 days.

const response = await fetch("https://nodvian.cloud/api/v1/auth/signup", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${NODVIAN_API_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    email: "user@example.com",
    password: "StrongPass1!"
  })
});

const { user, session } = await response.json();
localStorage.setItem("nodvian_session", session.accessToken);

const token = localStorage.getItem("nodvian_session");
const response = await fetch("https://nodvian.cloud/api/v1/auth/user", {
  headers: { Authorization: `Bearer ${token}` }
});
const { user } = await response.json();

Passwords require at least 10 characters, uppercase and lowercase letters, a number, and a symbol. Reset links expire after 15 minutes and revoke the user’s existing sessions after use.

Objects are stored through healthy Nodvian host nodes. Nodvian does not silently fall back to another cloud when no node is online.

const objectId = crypto.randomUUID();
const bytes = await file.arrayBuffer();

const response = await fetch(`https://nodvian.cloud/api/v1/storage/${objectId}`, {
  method: "PUT",
  headers: {
    Authorization: `Bearer ${NODVIAN_API_KEY}`,
    "Content-Type": "application/octet-stream"
  },
  body: bytes
});

const response = await fetch(
  `https://nodvian.cloud/api/v1/storage/${objectId}/sign`,
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${NODVIAN_API_KEY}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({ expiresIn: 900 })
  }
);

const { url, expiresAt } = await response.json();

Signed links default to 15 minutes and can be set from 60 seconds to 24 hours. Downloads report X-Nodvian-Node and X-Nodvian-Cache headers.

Each REST insert, update, or delete creates a project event containing the table, operation, row ID, payload, and timestamp. Use the stream for live clients or polling when your environment cannot attach authorization to an event stream.

// Open a text/event-stream response with fetch so the
// Authorization header can be included.
const response = await fetch("https://nodvian.cloud/api/v1/realtime", {
  headers: { Authorization: `Bearer ${NODVIAN_KEY}` }
});

const reader = response.body.getReader();
const decoder = new TextDecoder();

while (true) {
  const { value, done } = await reader.read();
  if (done) break;
  console.log(decoder.decode(value, { stream: true }));
}

Create functions in the dashboard with a lowercase URL slug, response status, content type, and response body. Responses may use {{method}}, {{timestamp}}, and {{path}} placeholders.

curl https://nodvian.cloud/api/v1/functions/hello-world \
  -H "Authorization: Bearer $NODVIAN_API_KEY"

Hosts provide storage capacity to the network. Get approved, create a private enrollment key, install the package for your system, and keep the service online. Enrollment keys start with ndv_node_ and must remain private.

# Ubuntu x86_64
curl -fLO https://nodvian.cloud/NodvianNode-Linux-amd64.tar.gz
tar -xzf NodvianNode-Linux-amd64.tar.gz
cd nodvian-node-linux-amd64
sudo ./install.sh
sudo nano /etc/nodvian-node.env
sudo systemctl enable --now nodvian-node
sudo systemctl status nodvian-node --no-pager

The environment file at /etc/nodvian-node.env contains NODVIAN_NODE_KEY, region, storage size, storage path, and config directory. After editing in nano, press Ctrl+O, Enter, then Ctrl+X.

Read the complete host requirements

Every JSON error includes a human-readable message. Check Project Logs for API, database, authentication, function, storage, and security activity.

• Keep project and enrollment keys in server-side secrets.
• Create separate keys for development and production.
• Use read_only whenever writes are unnecessary.
• Restrict browser-facing keys to your exact application domain.
• Revoke a key immediately if it appears in source control or logs.
• Use signed URLs instead of exposing API keys for file downloads.
• Treat user access tokens like passwords and clear them on logout.
• Review Project Logs and authentication rate limits before launch.