Skip to main content

​
Four commands

1

Install the CLI

npm install -g @elding/cli
2

Sign in

elding login
Your browser opens for authorization. The token is then stored locally with chmod 600.
3

Create a set and add your keys

In the dashboard, create a set such as dev and add your keys. Then link your project:
elding init
4

Run your application behind the proxy

Prefix your usual command with elding proxy --:
elding proxy -- node app.js
Your secrets are loaded inside the proxy, never into your application’s memory.

​
Add it to npm run dev

To make protection automatic, add elding proxy -- to the dev script in package.json:
package.json
{
  "scripts": {
    "dev": "elding proxy -- next dev"
  }
}
Now start your application as usual. The key is protected transparently: 
npm run dev
This works with any command: next dev, vite, node server.js, nodemon, and more. Your workflow stays the same; Elding runs on top of it.

​
The key moment

Your code only needs one line. configure() handles everything:
app.js
import OpenAI from "openai";
import { configure } from "@elding/sdk";

const openai = new OpenAI(
  await configure("OPENAI_API_KEY", "https://api.openai.com")
);
// the real key never enters your application
Now try logging the key: 
console.log(process.env.OPENAI_API_KEY); // → undefined or {{OPENAI_API_KEY}}
The OpenAI request still works: the proxy injects the real key at the last moment and locks it to api.openai.com. Your application, AI agent, and dependencies only see a placeholder. The real key does not exist anywhere in your process.

​
What’s next?

Understand the proxy

Learn how injection and host locking work.

run vs proxy

Choose the right mode for your use case.