Integrations and tooling that connect systems to the rest of the world: payments and KSeF, domains, Discord and webhooks, service-to-service APIs, MCP servers and bots. Each one built around a specific system.
A terminal tool for managing many repositories at once. From one place it shows the state of the whole workspace, does batch syncs, handles PRs, issues and contribution stats. It has a TUI surface for people and a prompt-free JSON CLI for scripts and automation.
The integrations of the Flaem hosting platform, each connected separately with keys in the operator panel: payment gateways with BLIK entered right in the panel, KSeF with VIES and NBP exchange rates, domain registrars with a fallback order, DDoS protection, text messages and Discord. Migration from WHMCS, Pterodactyl, Convoy, Virtualizor and cPanel always starts with a dry run, and a billing bridge lets you stay on WHMCS, Blesta, HostBill or Paymenter. Everything else connects through the REST API, signed webhooks, Terraform or an MCP server.
Gyred wires together the tools AI agents actually work in: Claude Code and Codex as session engines, repositories through vulp and gh, notifications on Discord, Telegram and Web Push, and an MCP server the sessions use themselves. A plugin adds a notification channel, a tool for sessions, a screen or an account usage reader, and the Discord bridge gives every session its own text channel.
Bots, webhooks and automations of the Plazer messenger that also work in end-to-end encrypted channels: a bot is a participant with its own keys there, not a hole in the encryption. Webhooks accept the popular embed format, "when X, do Y" rules are set up without code, and GitHub, Steam and Spotify accounts and bridges to other messengers are connected in settings.
The integrations of the VulCode client panel: a service-to-service channel through which the panel changes the plan of VulBio pages, suspends, resumes and cancels them, while a nightly reconciliation evens out any lost signal. Plus a Flaem licence delivered with a ready install command, wallet top-ups through Stripe and notifications by email, Discord message and Web Push following the client's preferences. Application errors reach the team channel with personal data scrubbed.
The integrations of the WaveHost client panel: VPSs created on Proxmox VE nodes through a job queue, game servers in Pterodactyl with console and power from the panel, Stripe payments with a signed webhook and a shop that pulls its offers from the brand's website on its own. The panel watches node resources and takes packages that no longer fit off sale, and every support ticket gets a private Discord channel from which the team answers straight into the panel.
The integrations of the Aphrodi agency's website and panel: the contact form, newsletter, referral links and analytics events reach the team's channels through webhook-proxy, and an analytics bot on the team's Discord answers with reports on traffic, pages, events, FAQ and referral links, posts a daily report on its own and announces crossed milestones. The client panel bills through Stripe and notifies through Web Push, and the content of every page in seven languages is available as clean JSON for AI assistants.
The internal API through which the VulCode client panel runs a hotel's subscription in Atrium: reading its state, setting the plan with the end of the paid period and suspending it with a stated reason. The client cannot change the plan, because none of their routes writes it, and the API is guarded by a shared secret in the X-Service-Token header: with no secret configured it answers 503 instead of running unauthenticated.
The internal API through which the VulCode client panel puts a venue on the free, trial or pro plan, suspends and unsuspends it. The plan only changes from outside, the owner manages nothing but invoicing details, and when the period ends the venue falls back to the free plan on its own without losing data. Every call lands in the venue's activity log with the caller named in the X-Service-Actor header.
Production bots running our brands' servers. Ticketing with team pings, welcoming new members, email verification and role hygiene - all tailored to a specific server. They take load off support and keep the community tidy without manual work.
A middleware layer between our services and Discord webhooks. It queues events per target, respects 429 limits and retries 5xx errors, so notifications do not get lost during traffic spikes. A single point through which all outbound communication passes.
A set of diagnostic scripts that watch the health of our infrastructure. They catch config drift, secrets committed to repos, expiring certs, dead links, missing backups and occupied ports. Routine work reduced to a single command.
Our own GitHub statistics API powering dualfroz.com, vulcode.com and profile READMEs: raw JSON and SVG cards with commits, languages, frameworks, tests, streaks and open source contributions. The collector holding the GitHub token and the API that only reads ready snapshots never share secrets, and a Discord app answers the same questions from any chat.
Plugins for SCP: Secret Laboratory servers wired to Discord. Player sessions and stats in a MySQL database, in-game ranks assigned live from roles, player lookup by Discord, Steam or IP address, punishments with templates, and reports the staff accept and close from the Remote Admin panel, confirming the close with a reason on Discord.
A monitoring microservice that checks HTTP addresses, Docker containers and server resources every minute, opens and closes incidents, counts uptime with maintenance windows and sends alerts to Discord without flooding the channel. It also tracks content changes on chosen pages, manages domains and mailboxes in Mailcow, and posts every new message from the team's mailboxes to a channel as a preview with link buttons and attachments.
An MCP server through which an AI assistant manages mail in Mailcow: domains and their DKIM record, creating and deleting mailboxes, aliases, and sending and reading messages over SMTP and IMAP. One conversation with the assistant instead of clicking through the mail panel for every new domain.
A Discord bot called with a ping that answers with Claude from a Claude Code subscription or with a model from a local Ollama. Parameters before the text set the model, channel context, temperature, limit, role and an answer scheduled for later, and a benchmark mode runs the same prompt through every local model and returns a table of results. Every channel has its own session that survives a bot restart.
Click a question and we answer in the chat.
Click a question and we answer in the chat.
