New Order Global

New Order Global

Overview

New Order Global Extension

AI-Powered Chrome Extension Builder. Describe what you want in plain English — AI generates custom tools that inject into any website. Includes a free built-in YouTube layout customization tool.

Chrome Extension

Manifest V3 extension, no build step required. Side-panel UI, AI Builder, and built-in YouTube customization tool.

Self-Hosted Server

Minimal Node.js/Express API with JWT auth, OpenRouter proxy, and optional MongoDB backend.

What's Included

  • • Describe → Generate → Iterate → Accept workflow for building any website tool
  • • Server-side AI proxy — your OpenRouter API key stays on your server
  • • Per-tool isolated storage with export/download support (CSV, JSON)
  • • Multi-model selection — pick any OpenRouter model your key has access to
  • • Conversation history — full context for iterative refinement of tools
  • • Built-in YouTube New Order with 8+ modes, volume boost, notes, comment search, and more

1) Install extension

Load unpacked in Chrome/Edge/Brave.

2) Run server

Local dev at http://localhost:3001 or deploy to cloud.

3) Point extension

Set BASE_URL in core/api-client.js to your server URL, reload, sign in.

download

Installation

check_circlePrerequisites

  • Chrome / Edge / Brave (Manifest V3 compatible)
  • Node.js 18+ and npm if you plan to run the server locally
  • OpenRouter API key (free tier is fine for testing)
  • Optional: MongoDB URI if you prefer DB storage over JSON files

routeChoose your path

  1. Trying it solo? Keep the server on http://localhost:3001 and point the extension there.
  2. Sharing with others? Deploy to Render/Heroku/Railway and switch the extension BASE_URL to your cloud URL.
  3. Switch anytime: edit core/api-client.js in the extension, then reload it in chrome://extensions.

Chrome / Chromium Browsers

  1. Navigate to chrome://extensions in your browser.
  2. Enable Developer mode using the toggle in the top right corner.
  3. Click Load unpacked and select the extension directory.
  4. Pin the extension icon to your toolbar for easy access.

Microsoft Edge

  1. Navigate to edge://extensions.
  2. Enable Developer mode.
  3. Click Load unpacked and select the extension directory.

Brave Browser

  1. Navigate to brave://extensions.
  2. Enable Developer mode.
  3. Click Load unpacked and select the extension directory.

Server Setup

Configure and start the self-hosted API server locally.

cd "global-order-server-opensource" cp .env.example .env # Fill in JWT_SECRET and OPENROUTER_API_KEY npm install npm run dev

keyRequired Environment Variables

  • JWT_SECRET: Long random string. Generate with: node -e "console.log(require('crypto').randomBytes(48).toString('hex'))"
  • OPENROUTER_API_KEY: Your OpenRouter API key from openrouter.ai/keys
  • MONGODB_URI (optional): Needed for persistent data; file storage works out-of-the-box if you leave this blank in the OSS build.

Point Extension at Your Server

Edit the extension's core/api-client.js (line 6):

const BASE_URL = 'http://localhost:3001'; // local development

The server starts on http://localhost:3001 by default.

Quick Connection Checklist

  • 1) Start server: npm run dev (shows "Listening on 3001").
  • 2) Reload extension in chrome://extensions after editing core/api-client.js.
  • 3) Sign in via the extension popup with the same account you use on the server.
  • 4) If requests fail, check CORS/URL: ensure BASE_URL matches the server console URL exactly.

What to change vs. leave alone

  • Change: BASE_URL in core/api-client.js to your local/cloud server.
  • Change: Your server .env secrets (never commit them).
  • Leave: Manifest permissions, extension ID, and service-worker filename (needed for MV3).
  • Optional: UI colors / branding in CSS, but re-load unpacked after edits.

Cloud Deployment

Deploy your server to cloud platforms like Render, Heroku, or Railway.

cloud_uploadRender Deployment

  1. Push your server code to GitHub
  2. Go to render.com and create a new Web Service
  3. Connect your GitHub repository
  4. Set build command: npm install
  5. Set start command: node server.js
  6. Add environment variables in Render dashboard (copy from your local .env — at minimum JWT_SECRET and OPENROUTER_API_KEY)
  7. If using MongoDB, add MONGODB_URI; otherwise the OSS build uses JSON files on disk.
  8. Deploy and copy the Render URL (e.g., https://your-app.onrender.com)

dnsUpdate Extension URL

After deployment, point the extension at your cloud server:

const BASE_URL = 'https://your-app.onrender.com';

Reload the extension in chrome://extensions to apply changes.

Troubleshooting

  • • 404/ERR_CONNECTION_REFUSED: Verify the cloud app is live and port is 3001 or set by your host.
  • • 401/Invalid token: Make sure you sign in on the extension with the same server URL you deployed.
  • • CORS blocked: set FRONTEND_URL or allow the extension ID in the server CORS config if locked down.

Configuration Reference

VariableDefaultDescription
JWT_SECRETRequiredCryptographic key for signing auth tokens
OPENROUTER_API_KEYRequiredYour OpenRouter API key
PORT3001HTTP port
STORAGEfilefile (JSON) or mongodb
ALLOW_REGISTERtrueSet to false to disable account creation
ALLOWED_ORIGINSemptyComma-separated CORS allowlist
rocket_launch
Managed Service

Skip the Setup

Don't want to self-host? Use our fully managed platform with everything already configured.

Access Platform arrow_forward
shield

Security Protocols

Never Commit .env

Your .env file contains sensitive keys. Never commit it to version control.

Strong JWT Secret

Generate a cryptographically secure random JWT_SECRET for any real deployment.

Lock Down Registration

After creating your account, set ALLOW_REGISTER=false to prevent others from signing up.

CORS Allowlist

Set ALLOWED_ORIGINS to your extension ID if your server is publicly reachable.