2383 applications
Reconner screenshot thumbnail

Reconner

Hunting for the hole is only half the job, because a scanner alert nobody believes wastes more time than the bug itself. Add a domain, CIDR, or bug-bounty scope and Reconner builds the map first: passive and active subdomain enumeration, live HTTP probing and fingerprinting, JavaScript analysis that digs endpoints, secrets, and API keys out of bundles, plus parameter and hidden-param discovery. Then it attacks what it mapped with a context-aware engine covering reflected, stored, and DOM XSS, SQL, NoSQL, SSRF, IDOR, LFI, SSTI, XXE, injection, and open redirects, and every candidate has to survive differential, out-of-band, or control-based proof, re-verified before it is ever reported. Blind issues are not dropped either: OAST callbacks catch out-of-band SSRF, RCE, SQLi, and SSTI that never respond inline. Networks get the same treatment, with port scanning, service detection, network-CVE checks, and IP-camera auditing. Findings land in a live dashboard streamed over WebSocket, with an attack-path view, coverage ledger, monitoring diffs, and HTML, Markdown, and PDF reports, while Telegram can alert you and even start, stop, or resume scans remotely. Run it only against assets you own or are authorized to test; behind a VPN and TLS it becomes your private proving ground. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
OpenGrokBot screenshot thumbnail

OpenGrokBot

OpenGrokBot gives you always-on AI teammates that live on your own hardware, each with a computer of its own. Every teammate is a folder with a persona and hard boundaries, a thread in your sidebar, and a contained machine with its own browser profile, workspace, and persistent memory that survives between asks. You manage the crew from a workbench-style web client: message one teammate or the whole group, watch its browser screen live, set routines like a morning digest, and check what each one used today. The safety model is the point: credentials live inside the teammate's own browser profile, so at a login wall it asks you to take over its screen instead of asking for a password; standing instructions change only through a diff you approve; and a teammate cannot approve its own holds. Teammates hand work to each other under an allowlist with a hop limit, optional daily token ceilings stop spending for the rest of the day, and a stop button kills even a shell command mid-flight. Computers can be a Docker container per teammate, or Docker-free local browsers with sandboxed commands. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Narralume screenshot thumbnail

Narralume

NarraLume is a writing studio for long novels where the AI proposes and you dispose, so a book stays yours across tens of thousands of words. Everything lives around the story bible: your stated intent, outline, entities, confirmed facts, relationships, chronology, and foreshadowing, kept as the single source of truth that planning, drafting, and review all read from. You can write chapters by hand in the studio, save versions and comments, ask for a selection edit, or delegate a chapter, a run of chapters, or a whole quick-creation plan to a model; whatever comes back arrives as a candidate with diffs, never as silent edits to your manuscript or canon. Review findings come with evidence you can accept, reject, or mark as false positives, and when generated prose collides with a locked fact the task stops and waits for your ruling instead of improvising around it. The run center keeps every AI job's steps, model calls, and checkpoints recoverable, the long-form lab searches story memory and previews plot impact without touching the book, and delivery ends with quality checks, exports, snapshots, and full-library backups. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
AsoBeast screenshot thumbnail

AsoBeast

AsoBeast keeps score of your app in the App Store and Google Play, so you always know which keywords you rank for, which ones moved, and what to fix next. Paste a store URL and tracking starts on import: rankings are checked daily in your home storefront and any other market you add, and every keyword is scored for popularity, difficulty, and opportunity so you can tell a winnable term from a vanity one. The dashboard leads with your keywords in the top 10, this week's movement, and an Action Center that turns the data into specific moves, like defending a keyword where two new rivals just entered the top 10, with the reason and the fix spelled out beside each item. Competitor listings are diffed over time, so a rival's new title, subtitle, version, or release notes show up as a before-and-after entry instead of a surprise. Metadata snapshots keep the raw store payload, localization and keyword field analysis shows wasted words, reviews feed the audit score, and the same data is exposed to your AI tools through the built-in MCP server. Registration closes itself once your owner account exists, and store requests run from your own server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Overclick screenshot thumbnail

Overclick

OverClick is the task board where your AI agents clock in: you write the assignments, they claim the work, and you stamp what actually got done. A card here is a contract, not a ticket: what should happen, why it matters, and a plain-language test script that says how to confirm it, all written before anyone starts. You tell your agent to grab the next task, and it claims the card over MCP, declares the CLI and model it really runs on, receives a self-contained briefing with the mission context and branch convention, and the card slides into progress. When it finishes, the handoff lands with a summary, evidence, branch and pull request links, and measured telemetry, the tokens per model and minutes the run actually took, read from the session transcript rather than guessed. Every card keeps three roles straight, who asked, who executed, and who reviews, and only a human can mark it validated; reopening with a comment puts your note in front of the agent's next claim. Big decisions can start as RFC cards whose approval spawns the execution cards, and insights roll up what each project, mission, and model consumed. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Netra screenshot thumbnail

Netra

Netra watches your network from the side, plugged into a switch mirror port, and turns everything it sees into a live picture of your traffic without ever sitting in the forwarding path. A single binary loads its eBPF collectors in the kernel, so aggregation happens before packets reach user space and multi-gigabit mirror feeds stay observable instead of dropping samples. The dashboard opens on totals, protocol share, and traffic trends, then lets you drill into flows by address, port, domain, or service, check which countries your traffic talks to on a world map, and read the internal topology as a live graph. Domains surface passively from TLS handshakes, public addresses are enriched with country and organization data, and heuristic detectors flag scanning, flooding, and single-host surges, pushing alerts to your team chat with an optional AI-written explanation. You can ask the built-in assistant questions about real recorded history, connect external MCP servers so it can call your own tools while it answers, and stream flows onward to Kafka for other consumers. History rolls into compressed columnar files on a schedule and stays queryable for a month by default. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Deploy
Shell Online screenshot thumbnail

Shell Online

Shell Online lets a terminal session running on your own computer follow you to any browser, so your coding agent keeps working while you are away from your desk. Prefix the command you already run, such as shell claude, shell codex, or shell opencode, and your terminal prints a link, a password, and a QR code that open the same live session on a phone, tablet, or another computer. You watch output as it happens and reply to prompts from wherever you are, and closing the browser leaves the process running until it exits on its own. Inviting a teammate takes the same link: share it read-only so they can watch without typing, or let them type into the session with you. Terminal traffic is end-to-end encrypted by default, file access stays off until you deliberately expose a chosen directory, and a scoped MCP grant can let another agent inspect or steer a session for a limited time. With an account, linked machines and their sessions gather in one web app with team sharing. The relay the sessions pass through can run on your own server with the standalone Docker deployment, pointed at by the unchanged CLI. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
HAProxy Manager screenshot thumbnail

HAProxy Manager

HAProxy Cluster Manager puts a web console on top of HAProxy, so you publish services, issue certificates, and cluster nodes from forms instead of hand-editing haproxy.cfg. Publishing a service takes two inputs, the public URL and the backend address, and the wizard builds the frontend, backend pool, host condition, routing rule, HTTPS listener, certificate, and HTTP redirect, with a preview of the exact configuration before anything applies. Every change is rendered and checked with haproxy -c before it is written, and a failed reload rolls back to the previous file automatically. Certificates come from Let's Encrypt through acme.sh, using HTTP-01 or DNS-01 with about 190 DNS providers, and renewals reload HAProxy and push the new certificate to every node on their own. Any number of nodes share one virtual IP through Keepalived: configuration and certificates sync between them, only the node holding the address is editable, and the dashboard flags split brain, an unclaimed virtual IP, or a node running stale configuration. You can gate services behind basic sign-in or OIDC single sign-on enforced by HAProxy itself, watch traffic statistics and logs, take transition alerts by email, Pushover, or webhook, and expose Prometheus metrics and Home Assistant entities. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Deploy
AliangBoard screenshot thumbnail

AliangBoard

AliangBoard puts every Kubernetes cluster you run behind one web panel, where you manage resources yourself or ask an AI agent to do it with your approval. Connect each cluster with a bearer token or basic auth and the panel persists the connection, so switching clusters, namespaces, and workloads takes one click instead of another kubeconfig. More than thirty resource types stay in sync: create workloads, services, ingress, config, storage, and RBAC through structured forms, edit anything as YAML, apply multi-document manifests at once, and delete optimistically with automatic rollback when the API refuses. Pod work goes deep: a tmux-backed exec terminal survives browser refreshes, port-forwards resolve services to their backend pods, files move up and down with progress, and debug containers inject into running pods without restarting them. Day-two operations are buttons, not flag memorization: scale, rolling restart, rollout undo, manual CronJob triggers, and node cordon or drain. Global search, a layered namespace topology, live event streams, and CPU and memory metrics keep orientation effortless. Then there is the operator: an Agent workbench and MCP server let your LLM read logs, debug containers, and propose changes in natural language, while every write waits for a human click and lands in an audit log that names who did what. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
OpenGTM screenshot thumbnail

OpenGTM

OpenGTM turns a market, a list, or a workbook into enriched, researched, ready-to-contact prospects on servers you control. Give it a market and it sources companies and people; hand it a CSV or a Clay table and it maps the columns into a shared record library. Enrichment columns run as waterfalls that try providers in cost order until a field is filled, and before anything spends a cent you see best and worst case estimates, with a workbook budget ceiling that halts paid calls on its own. Research columns send an agent to answer the hard question for each row, and the answer keeps citations to the pages it actually fetched, so a human can audit the claim before outreach. Live audiences segment your records and watch for hiring and buying signals, refreshing on schedules and firing automations when a prospect heats up. Finished rows flow out to HubSpot, Salesforce, Slack, Sheets, Airtable, Instantly, Smartlead, webhooks, or a warehouse, while every cell keeps a trace of provider attempts, latency, and cost. Your own agents get the same workspace through a REST API, webhooks, and an MCP server with scoped read and write tokens, and a seeded zero-key demo means the team can explore the whole loop before adding a single provider key under Settings. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
SubLane screenshot thumbnail

SubLane

Five teammates sharing three AI subscriptions usually means a password in a group chat; SubLane replaces that with a gateway you host, where accounts are pooled and every person gets a managed key. Connect Codex, Claude, Antigravity, and Grok Build subscriptions once, by browser OAuth or credential import, and the gateway snapshots each account's quota windows and allowances so routing knows who still has room. Add API channels for OpenAI-compatible services alongside the subscriptions, then group everything into resource pools with model allowlists, conversation affinity, concurrency controls, and cooldown recovery for accounts that hit a limit. Each member receives a personal key scoped to one group, with its own expiry, rate and concurrency limits, and an allowance measured in tokens, internal dollars, or estimated quota share; keys can be paused or revoked without touching anyone else. Whatever the client speaks, the gateway answers: OpenAI Responses and Chat Completions, Claude Messages, and Gemini formats flow over HTTP, SSE, or WebSocket, independent of which subscription actually serves the request. Administrators watch per-member and per-model usage charts, activity heatmaps, and request diagnostics, bind a fixed outbound proxy to any account, and apply workspace content rules before dispatch. It all runs as one Go process with SQLite and an embedded dashboard, backed up and restored from the interface. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
AgenTerm screenshot thumbnail

AgenTerm

AgenTerm lets your AI agent work inside a remote computer's terminal with the owner's permission, through a relay server you host yourself. Your agent connects to the server over MCP and creates an invitation, single-use and expiring in fifteen minutes by default, or reusable across several devices; you privately share the generated connection command with the person who needs help. That person runs a small client on macOS, Linux, or Windows, reads what access means, and authorizes it; the client then dials out to your server, so the target computer needs no SSH service and no open inbound port. The agent can then run one-off commands with a chosen working directory, environment overrides, and timeouts, receiving stdout, stderr, and exit status, or hold an interactive session open, reading output as it arrives and typing answers to prompts. The person at the keyboard watches every command and its output in the client and can disconnect at any moment, and the client reconnects by itself after a network drop. Use it to troubleshoot a colleague's machine without swapping logs, help family through a terminal problem, or drive a development box with no agent or model account of its own. The relay itself is a single Go binary guarded by a management key, deployed with Docker Compose or systemd, with in-memory sessions and a health endpoint. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
AGenUI Studio screenshot thumbnail

AGenUI Studio

AGenUI Studio turns a written description into a working interface card: an AI agent generates the UI, binds it to your APIs and data, and packages it so it runs anywhere, no Studio required. Bring your own model by entering any OpenAI-compatible or Anthropic Messages endpoint and key in the console settings, and generation proceeds contract-first, steered by design rules you publish as versioned Markdown revisions. You preview each card live as it is generated, then refine it over multiple turns while every component, binding, and action you did not target stays protected from accidental edits. The console also manages the supporting cast: a local knowledge base, API definitions, and reusable operators, all starting from bundled demo data you can swap for real services whenever you are ready. When a card is finished, download it as a self-contained Runtime Package carrying its data sources, bindings, actions, and operators, and execute it with the bundled Card Runtime inside your own application, or register a delivery target and publish straight from the workbench over a callback or a message queue. Applications subscribe to native run events over HTTP and SSE, and production deployments can replace the local defaults piece by piece, MySQL for storage, Redis for hot state, MCP services for knowledge and data, while the packages keep the same contracts. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
OpenSkyCam screenshot thumbnail

OpenSkyCam

OpenSkyCam records a sky-facing IP camera around the clock on hardware you own, and searches the footage for meteors, planes, and anything else that moves. A small Linux relay by the camera copies the RTSP stream into one-minute MP4 files without re-encoding, kept on your disk under a rolling 40-day window: browse by day, scrub by hour, zoom into the 4K frame, download originals. Workshop workflows sample frames from any time window, run up to four detection or classification models over them, and sort each frame into buckets by class, score, count, time of day, or motion, once or nightly as footage lands. Detections of one object link across a recording into tracks labeled moving, stationary, or brief, so fixed stars and porch lights are discarded and aircraft kept. A trained night detector for planes and meteors ships with the project; every detection waits in a review view where you confirm or correct its label and box, then freeze the approved set as a versioned training dataset. The processor lives on your machine too (Apple or NVIDIA GPU, or plain CPU), and the footage itself never leaves your disk. Every website action is also a /v1 API call, and an MCP server lets an AI agent find last night's clearest meteors, take a photo at any second of stored video, or schedule the next workflow. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
PrettyPleasePrint screenshot thumbnail

PrettyPleasePrint

Pretty Please Print turns one office's shared 3D printer into an invite-only request board: colleagues upload a model and follow it from request to delivery. Requesters upload an STL or 3MF file, or start from a Printables link the owner enabled, and the mesh renders in the browser, auto-framed and draggable, so everyone checks the geometry first. Every request becomes a ticket that the printer owner moves through Requested, Accepted, Printing, and Delivery, or declines with a reason, and requesters can withdraw their own print before it reaches the bed. Slicer specifics like layer height, infill, supports, and temperatures ride along as notes on the ticket, a low, medium, or high priority keeps the owner's queue ordered, and a conversation thread on each ticket replaces lost chat threads. The owner curates the materials and colours on the shelf, with swatches and a rainbow whatever option, and defines the tips requesters can offer, preferred ones starred. Finished jobs collect in a filterable history: Print again reopens the form with the model copied server-side and fields adjustable, and one click sends a model straight to PrusaSlicer. Accounts are invitation-only; access can be revoked with a global sign-out, every change lands in an audit trail that cannot be edited, and the same tickets are exposed over a JSON API documented in OpenAPI 3.1 with a Swagger console. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Headroom screenshot thumbnail

Headroom

Headroom answers the question every multi-plan AI subscriber asks mid-task: which of my accounts still has room to work? It puts the live limits, reset times, credits, and spend of Claude, Codex, Cursor, Copilot, Grok, Antigravity, and Vercel AI Gateway accounts on one self-hosted dashboard instead of seven provider pages. Connect each account once, through its official CLI sign-in or a credential import, and a background scheduler refreshes every figure on schedule, renews tokens before they expire, and keeps 90 days of readings. Five-hour sessions, weekly pools, per-model limits, credit balances, banked resets, and on-demand spend sit side by side, and unreported figures show as unknown rather than a fake zero. Compare ranks same-provider accounts by the room they have left and names the one to use next, while Timeline lays every reset window on a two-week calendar. Analytics charts when you work, when you run dry, and whether each plan fits, and Wallet totals subscriptions, usage spend, and top-ups in one currency with renewals and budget alerts. In-app notices, Telegram messages, and signed webhooks warn about low limits, expiring resets, and broken sign-ins, and optional automations can spend a banked Codex reset or log a credit top-up the moment it lands. Personal, work, and side-project accounts stay separate under one owner login with passkeys and a Privacy Mode that blurs emails on screen. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Fonrex screenshot thumbnail

Fonrex

Good European market data is either expensive or wrong, so Fonrex runs it all on your server: a self-hosted API serving per-listing prices, cross-checked fundamentals, DCF valuations, and factor models for European and US shares, with no subscription or per-call meter. Every price is stored per listing in its own currency and dated by trading session, so AIR.PA resolves to Airbus rather than a same-ticker US namesake, and one ISIN can carry many listings cleanly. Fundamentals are cross-checked between sources first; figures that disagree with the consensus are rejected, and every answer names the sources it came from. Value any company three ways with FCF, EPS, and dividend DCF models, compare them side by side, and stress the result with a WACC by growth sensitivity matrix. Factor tools return Kenneth French returns for the US, Europe, and developed markets, compute listing factor exposure, and price equity with the risk-free rate of the right currency, alongside FRED and ECB rates, Treasury curves, and Eurostat indicators. Daily history spans ten years, split-adjusted with a dividend-adjusted close; live ticks stream over WebSocket, indicators and a screener run on your stored prices, and deduplicated news arrives per ticker or as a global feed. Results plug into OpenBB Workspace, Google Sheets, Python notebooks, and Zipline backtests, so spreadsheets, dashboards, and research pipelines all read the same numbers. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
BrightBean Chat screenshot thumbnail

BrightBean Chat

BrightBean Chat is a self-hosted chat automation platform that builds visual flows once and runs them across Instagram, WhatsApp, Messenger, Telegram, SMS, and email, so your audience automations live on your server instead of a per-contact subscription. You drag conditions, delays, randomizers, data collection, and message nodes onto a canvas, test the draft while the live version keeps running, then set it live with every save versioned. Flows start from keywords, comment-to-DM triggers, story mentions and replies, follows, ref URLs, QR codes, or calls to the public API. Every channel lands in one shared inbox where teammates assign conversations, label them, schedule replies, and take over from the bot, which pauses the automation for that contact. Contacts carry custom fields, tags, and segments that stay unified across channels, and imports and exports keep the list portable. Broadcasts and multi-step drip sequences check opt-outs and each platform's 24-hour messaging window before sending, pace themselves per channel, and show exactly who will receive a message and who is skipped. Per-node counters track sent, delivered, failed, and clicked, while a bearer-authenticated REST API and signed webhooks hand leads to Make, Zapier, n8n, or your own systems. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy