Overview
How the account pool, your API keys and the server are doing right now.
- Status
- Loading…
Sessions
Every Instagram account in the pool. Open one to manage its credentials, proxy and limits.
Add account
Log an Instagram account into the pool. Two-factor codes and security challenges are handled step by step.
API keys
Keys your customers send in the X-API-Key header. Each key's plan caps its requests per UTC minute, day and month (plans are set up on the Plans page); an unknown or revoked key is served like a request without a key.
Plans
Every API key is on one plan. A plan caps the key's requests per UTC minute, day and month (empty or 0 = unlimited); a change applies to every key on the plan at once. Price and the Public switch only change what the landing page, the docs and GET /api/plans show — nothing is billed.
Activity
The latest 200 server log entries, newest first: lookups, background browsing, post-login runs, logins and errors.
Statistics
Requests, capacity and account health from the statistics database. Kept across restarts and deploys; all times are UTC.
A past month is shown: the month selector changes the month totals, endpoints, keys, statuses and accounts. The chart, Today, Peak, Active accounts and Capacity are always live.
Show as a table
- Status
- Loading…
Profile Plus
Apply a prepared content folder — profile picture, posts and stories — to one account.
Settings
Telegram — status reports and alerts delivered to your admins through a Telegram bot.
Settings
Saved on this server and applied at once — unless a field is marked restart. A value saved here wins over .env; Reset goes back to .env or the built-in default.
Applied at once, no restart. API keys follow the limits of their plan instead (API → Plans).
Changing it signs out every other browser. Only a bcrypt hash is stored (in .env).
A new license applies after a restart of the server. The next deploy keeps whichever license expires later (this server’s or the one in the local .env).
- Status
- Loading…