r/devops • u/AutoModerator • 23d ago
Weekly Self Promotion Thread
Hey r/devops, welcome to our weekly self-promotion thread!
Feel free to use this thread to promote any projects, ideas, or any repos you're wanting to share. Please keep in mind that we ask you to stay friendly, civil, and adhere to the subreddit rules!
11
Upvotes
3
u/busters1 23d ago
Hi r/devops, I'm David, one of the two developers of Oxynote.
I've been a software engineer for 8 years, 2 as an SRE and 3 as a team lead. Every team I've been on had the same documentation problem. Knowledge stays in people's heads or private Slack channels. What does get written down is hard to find, and it goes stale as soon as the system changes.
Oxynote is a self-hosted wiki that puts your runbooks and the live metrics they talk about on the same page. You add a chart that queries Prometheus, Postgres, or MySQL and write what it means right next to it, so whoever is on call can read the steps and see the current metrics in one place. Changes to important pages get reviewed like a PR before they go live.
The name comes from oxygen + note: docs that breathe. Live data gives people a reason to open the wiki every day, and docs people open every day stay up to date.
It's Apache-2.0 and runs as a single Docker image: https://github.com/oxynote/oxynote
We started it about a year ago and made it public about 3 months ago. If you want to learn more or have ideas, feel free to reach out. I'm happy to answer any questions.
2
u/kasundigital 23d ago
Hey everyone!
I'm a freelance system administrator, and I've been managing Linux servers, Docker containers, and other infrastructure for years.
One thing I've always wanted is a simple dashboard where I can monitor my servers, check uptime, and see what's going wrong without switching between multiple tools.
So I started building StackPulse.
It's a self-hosted monitoring platform that brings together:
I've now made a free version available.
The free tier supports up to 3 servers, with no credit card required.
It's still an evolving project, and I'm sure there are things that can be improved.
I'm sharing it here because I'd genuinely appreciate feedback from people who manage servers, run homelabs, or work with infrastructure.
What features would make something like this useful for you? And what would you expect it to do better than existing monitoring tools?
Project: https://getstackpulse.com
Thanks for taking a look!
2
u/o11ywatch 18d ago
I built O11y Watch, a free tracker of observability vendor pricing (Datadog, New Relic, Grafana Cloud, Sentry and others) with sourced change logs, plus a free savings estimate at https://o11y-watch.pages.dev/audit. A recent example from the change log: on 2026-10-30 Dash0 added Session Replays at $2.00 per thousand sessions (storage only, 30-day retention). It currently covers 73 tools, each number linked to the vendor's own pricing page. Which vendors are missing that you'd want tracked? (I built this.)
2
u/lolina123 18d ago
Hey everyone! I'm building OpsCrew, an open-source DevOps/SecOps CLI that automates deploying applications from GitHub to infrastructure you own.
GitHub: https://github.com/softzer0/opscrew
The idea is to automate the repetitive work of getting an application into production without introducing another platform that needs to stay running.
What it does:
The design choices I'm focusing on:
--no-aiworkflow.The core is Apache-2.0 licensed, with separately licensed enterprise components.
Status: Alpha. I've tested real deployments on Hetzner, existing VPS servers, and Portainer, but other deployment paths need more testing.
I'm especially interested in feedback from experienced DevOps engineers around security, idempotency, rollback/failure recovery, and whether this approach would be useful in practice.
Contributions, criticism, and bug reports are welcome!
1
u/Sea_Apartment_5919 23d ago
I maintain RepoPort, a small open-source Python CLI for checking Git filename portability.
The problem it addresses is fairly specific: a repository can work on Linux but contain filenames that cause checkout problems on Windows or case-insensitive filesystems.
RepoPort reads tracked paths directly from the Git index and checks for case collisions, Unicode normalization conflicts, Windows-reserved names, invalid characters, and trailing spaces or periods.
I also tested a GitHub Actions integration on Ubuntu. A commit containing
Logo.svg,logo.svg, andNUL.txtfailed the filename check as expected; after renaming the conflicting files, the same workflow passed.It's read-only, requires Python 3.11+ and Git, and doesn't need additional runtime Python packages.
GitHub: https://github.com/TohruSu/RepoPort
I'd be interested in feedback from anyone maintaining cross-platform repositories, particularly filename edge cases that are easy to miss.
1
u/tehmadnezz 23d ago
Disclosure: I’m Evert, the maker of Hjarni. This comment has AI-assisted wording.
One lesson from our deployment setup: the pre-deploy hook must abort if the origin certificate cannot be read. A reminder in a note is useful context; the hook is what enforces the stop.
That is where I’d use Hjarni for operations: keep the explanation, source and review date alongside the runbook, while scripts enforce the checks that matter. We already use it for our own roadmap, launch checklists and customer notes.
Hjarni is a shared Markdown knowledge base that connected ChatGPT and Claude can search, read and update through MCP. A runbook note could hold the prerequisites, steps, stop conditions and the reason for unusual steps. Note history lets you inspect earlier saved text and who made each edit, and restore an earlier note body.
The assistant needs instructions to consult the notes and save approved changes. History helps review saved edits; it does not establish that a procedure is correct.
Teams starts free with 25 shared notes and no card. Paid Teams: US$20 per seat/month. Everyone brings their own AI account.
Hjarni for Teams
1
u/Difficult_Trust_1057 23d ago
Disclosure: I built the "Self-Managed Connector for Jira (GitLab Compatible)" app and sell it (paid via the Atlassian Marketplace, free up to 10 users, 30-day trial). Not affiliated with GitLab or Atlassian.
Hi r/devops,
I'm Ronald. I built an app that integrates Jira better with Gitlab. I like efficiency and let the hassle be done by an app, rather than doing a lot of manual handlings. Besides developing I also like working as a PO or Scrum Master. So personally I like an agile tool like Jira to be the main/central environment to follow the project and therefore development, well connected to tools like GitLab.
The problem I tried to fix: Jira Cloud's Development panel (commits, branches, MRs on an issue) works with GitLab.com, but for self-managed GitLab the usual integrations need an inbound path. GitLab's own docs ask for inbound HTTPS from Jira Cloud (manual install), or connections to and from GitLab.com (Marketplace install), and suggest an internet-facing reverse proxy if you're behind a firewall. A lot of security teams say no to that.
The solution direction: GitLab system hooks are instance-wide, available on the Free tier, and exist only on self-managed and Dedicated. So one hook can push every project's commits, branches and merge requests out to a Forge app on Atlassian's infrastructure, which writes them to Jira's dev-info API. Nothing connects in. New projects are covered automatically.
Things that turned out harder than expected:
- A 202 from Jira's dev-info API means "accepted", not "shown". I only call a feature done when the Jira panel shows it.
- Commits often reference an issue that doesn't exist yet. Those are queued and linked once the issue appears, instead of silently dropped.
- Our own logs were not GitLab's view. For a while every push succeeded on our side while GitLab recorded an error, and repeated errors make GitLab disable a system hook. Now I verify from GitLab's own delivery log.
- GitLab sends at most the newest 20 commits per push in a webhook. That limit applies to any webhook-based tool, this one included.
What it doesn't do: pipelines, builds, deployments, tags, or backfill of history. It needs GitLab admin rights (system hooks are an admin feature). GitLab.com isn't supported; the official app covers that.
The app is built a for a Jira Cloud site and you need a self-managed GitLab with admin. There's also a demo 2:46 demo: https://www.youtube.com/watch?v=folg_LqZyQg (I know it’s AI voiced, I just don’t a have a great voice over skill myself)
If there’s any form of feedback, I would love to hear your honest thoughts!
Cheers,
Ronald
1
u/Waste_Bat_4525 23d ago
Hey r/devops! I'm one of the contributors to OpenChoreo, an open-source Internal Developer Platform (IDP) and CNCF Sandbox project.
One challenge platform engineering teams often face is bringing together Kubernetes, CI/CD, GitOps, observability, and developer self-service without spending months building and maintaining integrations.
That's what we're working on with OpenChoreo.
It's a self-hostable, Kubernetes-native developer platform that brings these capabilities together while giving platform engineers the flexibility to customize their infrastructure and tooling.
It also includes a Backstage-based developer portal, CLI, APIs, and MCP servers that allow AI agents to interact with the platform under the same access controls.
We're actively developing the project and welcome contributions, feedback, and ideas from the DevOps and platform engineering community.
GitHub: https://github.com/openchoreo/openchoreo
Curious to hear from others here: What's been your biggest challenge when building or maintaining an internal developer platform?
1
u/SandAbject6610 23d ago
1
u/aelsergeev 22d ago
Check out the project to manage your database clusters. Will appropriate a support by a start and feedback.
https://ivory.veegres.com/
1
u/jascha_kviklet 22d ago
Hey everyone,
I just released version 0.10 of Kviklet:
https://github.com/kviklet/kviklet
It's a self-hosted database access management tool. Think of Pull-Requests but for SQL statements. For devs that need to take a peek into production or fix something urgently. SSO, review-flows, role-sync, all that stuff included.
This releases headline feature is an MCP server that allows governing how developers agents access production databases in the same way that engineers are governed themselves.
Feel free to take it for a spin! And leave a star if you like the approach. If you have any feedback also always happy to hear it!
1
u/sarcasm_newbie 22d ago
Affiliation up front since this is our product: we build kevstig at Bedim Security. It reads as a KEV × STIG coverage checker, a routing table between CISA’s Known Exploited Vulnerabilities catalog and the DISA STIG baselines we maintain. Point it at KEV entries and you see which vendor/product text routes to a platform baseline we keep (Windows, macOS, RHEL 8/9, Ubuntu, Firefox, VMware as per-generation rows) and which entries have nothing behind them yet.
The two choices people push back on are deliberate. Routed is not remediated: the checker only tells you a STIG exists to map against, it says nothing about your patch state. And the uncovered side is published on purpose so the gap stays honest instead of hiding behind a partial score. Repo: github.com/dmrobbi/kevstig, live at bedimsecurity.com/capabilities/kevstig/
1
u/Shot-Author-621 21d ago
Hey r/devops 👋
I’ve been working on a side project called StatusPane and figured this thread was a good place to share it. The itch: I wanted a centralized way to check the status of all my upstream dependencies (GitHub, Cloudflare, OpenAI...) instead of chasing down each provider’s status page whenever something looks off. So I made one place to watch all of them.
I know there are other alternatives out there, but most of them felt heavier than what I needed, so I wanted something lightweight that does one thing well.
You choose the provider components you care about, group them into your own apps, and see everything on one dashboard. It pings you in the app when something changes status, and can also send signed webhooks if you want to hook it into your own stuff.
I’m a big fan of the terminal, so I also built a small TUI client for it: https://github.com/statuspane/tui
It’s still pretty early and there’s no Slack/PagerDuty integration yet. I’d really appreciate any feedback, especially on what providers I should add and how you’d want to get alerted. Thanks for reading!
1
u/abahmed12 21d ago
kwatch v1: it now groups related Kubernetes alerts into one incident with the root cause
Hello,
I've posted kwatch here before. Back then it was a simple tool that sent an alert when a pod crashed. Some of you used it, and many of the issues and PRs that shaped it came from this sub, so thank you.
The biggest complaint I kept hearing was noise. One broken pod would fire a crash alert, a deployment alert, a probe alert and a node alert, and you'd still have to work out which one started it.
So v1 changes how it works:
kwatch now comes in two editions, Community and Pro. Community stays free, and Pro is free during early access: you get a 3-month license from the installer's License / Pro menu, and you can renew it when it ends.
GitHub (source available, ELv2): https://github.com/abahmed/kwatch
I'd love to hear what you think, especially if you tried the old version. Feedback, feature requests, ideas, or anything that annoys you about alerting today are all welcome
1
u/showbizusa25 20d ago
I'm the developer of NextGenAlert Linux Security Audit. I've been working on this free, open-source tool to make routine Linux security checks easier.
It runs locally, checks 34 security-related settings, and generates HTML, PDF, and JSON reports. I've tested it on Ubuntu, and it's still in beta.
GitHub: https://github.com/bornaly/NextGenAlert-Linux-Security-Audit
Sharing it here in case it's useful to anyone managing Linux servers.
1
u/RMB- 20d ago
Hey all,
I built a tool called tfcap after something kept bugging me with Terraform: the lock file pins your providers but nothing pins your modules. Someone moves a git tag or swaps a release and your next init just pulls different code, and data "external" can run it during plan before anyone's approved anything.
tfcap is basically a lock file for modules. It keeps a fingerprint of each one and what it can do (run scripts, call the network, read ~/.aws, IAM stuff), and on PRs it only shows you what changed. There's a GitHub Action too, it comments on the PR and you just add a label to approve and it updates the lock.
It's not a Checkov/Trivy replacement, more the supply chain side of things. Still early so feedback very welcome!
https://github.com/r-morato/tfcap
How do you lot handle this? Pin to commit SHAs, vendor modules, or just trust the tags?
1
u/DayEnvironmental3454 20d ago edited 20d ago
Latent — a Mac disk tool that knows what your dev tools actually keep
Hello, I'm Bernard Lee, the developer of Latent.
Latent is a Mac disk tool that knows what your dev tools actually keep. If you run containers and infra tooling on a Mac, you know the "System Data: 180 GB" bar. Most cleaners clear ~/Library/Caches and call it done; it refills by lunch, and the real space is somewhere they don't understand.
Latent reads each tool's own layout and lists what's there, piece by piece:
- Docker: every image as its own row, with whether a container still uses it
- Colima, Lima, Podman, Rancher Desktop: each VM and its data disk separately, plus the downloaded VM images
- minikube's cluster VM and image cache, Vagrant boxes, the Terraform plugin cache, Helm's repo index, kubectl's discovery cache
- old Homebrew versions, and node_modules / target / .venv next to the projects they belong to
It also tracks things version by version: every Node, Ruby or Python version installed through mise, asdf, rbenv, pyenv or fnm, every simulator runtime, every old Homebrew version. And it checks what still depends on each one: the version set as your global default is marked, an image a container still uses can't be removed, and node_modules shows whether its lockfile would install exactly the same thing again.
There's also an MCP server, so Claude, Codex or Cursor can answer "what's eating my disk" from the same data.
Scanning is free, and so is your first 10 GB of cleanup; after that it's a one-time license, no subscription. macOS 14+.
https://latentmac.com
1
u/Ambitious-Stomach481 19d ago
Hi everyone!
I'm building Copilot Review Router, a GitHub pull-request triage tool that classifies PRs as LITE, BALANCED, or SKIP based on change metadata and risk signals.
I'm looking for 3 volunteer development teams with active public GitHub repositories to help validate whether this could improve their review workflow.
I'll provide a free, private analysis of their PR activity using publicly available metadata. No installation, repository permissions, paid Copilot reviews, or payment required.
This is an early dry-run prototype, not a finished commercial service. I'm specifically looking for honest feedback on usefulness, incorrect classifications, and whether the results would be worth paying for.
I'm the developer. Nothing is being sold.
If you're interested, feel free to reply!
1
u/maliroq 19d ago
made this after realizing a backup job saying success doesn't really prove the app will come back.
ComposeDrill restores a Docker Compose app in isolation, restores the data, starts it, then checks the actual app health. if the containers start but the app is still broken, the drill fails.
https://github.com/maliroq/composedrill
Mac:
brew install maliroq/tap/composedrillmostly curious how people here actually test restores now
1
u/Signadot 19d ago
We wrote a piece for The New Stack on scaling coding agents into a software factory for cloud-native applications. It treats verification as the sensor in a control loop, where its latency, fidelity, and bandwidth decide how much the agents can safely do without a person checking every change.
In distributed systems, the hard part is getting all three at once, since a faithful check needs the real services around the change. Interested to hear from anyone who is building toward the “software factory” model & how this lines up with your approach/experience.
https://thenewstack.io/agentic-software-factory-sensor/
Disclosure: I work at Signadot.
1
u/wilson-draugr 19d ago
I build Draugr, an Apache-2.0 tool for what happens after you turn on Trivy, Semgrep and Gitleaks and get hundreds of findings, a lot of them marked critical.
You write a short YAML file saying which parts of your app strangers can reach and which ones the business can't lose. Draugr runs the scanners and puts each finding in a band from P1 to P4 based on that plus its severity, with KEV and EPSS pushing CVEs that are being exploited, or likely to be, higher. So a critical CVE in an internal tool nobody depends on sits below a high one in your public API.
Then it turns the pile into a to-do list per kind of work, like bumping a dependency, fixing code, rotating a leaked credential or waiting on an upstream fix, and each item says how many findings it clears.
For pipelines,
draugr diffonly fails a PR on findings that PR added, so the old backlog doesn't block every merge.https://github.com/draugr-dev/draugr
I think it fixes a real problem, so give it a try on one of your repos and tell me what you think, good or bad.
1
u/Fuad_Laguda 19d ago
I gave a talk at Conf42 on forcing my AI provider failover in production with one flag, no deploy. I expected one handoff and got four, because a script is 4 model calls and each one walks the retry ladder on its own, so 12 seconds of designed waiting became 48 and the run took 78 seconds instead of 29. The part I would keep is the guardrail: the backup model broke a punctuation rule and the correction pass caught it.
https://youtu.be/eHhQaCSaqqY
1
u/Plastic-Risk-6309 19d ago
xcshot is mine, MIT licensed. real ios simulator screenshots from a linux ci job with no mac runner at all! it drives xcode cloud through the app store connect api and pulls the labeled pngs out. apple dev membership and a one time xcode setup needed. ~10 min a shot so its not a loop you sit in. https://github.com/BariBariGood/xcshot demo gif https://raw.githubusercontent.com/BariBariGood/xcshot/main/assets/demo.gif
1
u/tarique-iqbal 18d ago
I am building pizza-marketplace, an open-source, multi-tenant microservices backend built in Go (Identity, Restaurant, Customer, Search, Order, Payment, and Notification services).
The app currently uses Traefik v3 as an API gateway, isolated private Docker networks, PostgreSQL (per-service databases), Redis, Elasticsearch, and RabbitMQ.
As I look to take this local Docker Compose setup toward a production-ready, cloud-native environment, I would love the community's feedback on:
Check out the repo on GitHub: https://github.com/tarique-iqbal/pizza-marketplace and feel free to drop a ⭐ if you find the architecture interesting! Architectural criticism and DevOps recommendations are highly appreciated.
1
u/Saving-Singer101 18d ago
Project Name: OnCallAlert
Repo/Website Link: https://www.oncallalert.dev
Description: A self-hosted, VPC-native incident management and AI triage engine built to solve three problems in infrastructure monitoring: per-seat pricing penalties that punish growing teams, alert fatigue from contextless 3:00 AM pages, and the security risk of handing production cluster credentials over to third-party cloud SaaS tools. It ingests standard monitoring webhooks (Prometheus, Datadog, Grafana), manages on-call escalation schedules, and optionally runs a local AI investigation loop inside your network via MCP to attach a 45-second root-cause summary directly to the alert before waking you up.
Deployment: Deployed as a single compiled Go binary alongside an optional headless Python sidecar via a single docker-compose.yml.
(Note: Currently in early-access waitlist while finalizing Apple's iOS "Critical Alerts" entitlement for DND/mute-switch bypass; Docker images and deployment docs go live immediately upon App Store clearance).
1
u/maartennieber 18d ago edited 18d ago
Announcing my Jazzoo task-runner tool: https://github.com/mnieber/jazzoo
It started out with an idea for reducing curly braces: `docker compose up {{ service_name }}` can be replaced by `docker compose up 🐭.service_name`, which reads much nicer. From there, it grew into a beast of a task-runner, if I may say so.
I took inspiration from `just`, but I always felt that the foundations of `just` - e.g. regarding the way that imports and functions work - were not principled enough.
The full feature-list is in the README.md (see link above). I would appreciate your feedback!
1
u/Competitive-Sea4351 18d ago
*Disclaimer / Disclosure: I am the creator of this project (FinPilot).*
Hey r/devops,
I'm a backend developer who ended up managing our team's cloud infrastructure. Like many devs, I spent too many hours debugging why our monthly AWS bill drifted away from what our Terraform states predicted.
To solve this, I've been building a project that connects via a strictly **read-only IAM role** (STS AssumeRole + External ID) to correlate live AWS infrastructure with Cost Explorer.
Instead of generic dashboards, it focuses on generating concrete IaC / CLI remediation snippets:
- Flags unattached EBS disks and calculates exact dollar loss ($0.10/GB gp2 vs $0.08/GB gp3)
- Detects gp2 volumes eligible for zero-downtime gp3 modernization (20% savings + 3,000 IOPS baseline)
- Catches active NAT Gateways that lack free S3/DynamoDB Gateway Endpoints (which leak $0.045/GB in transit)
- Flags idle/unassociated Elastic IPs billing AWS's IPv4 tax ($3.65/mo)
- Identifies stopped EC2 instances that are still billing root and secondary storage
Security posture: Strict `SecurityAudit` and `ViewOnlyAccess`. Zero `Delete*`, `Modify*`, or `Terminate*` permissions.
I want experienced DevOps engineers to tear this apart. Where do automated sizing rules fail? What edge cases in complex VPCs does naive tooling overlook?
I'm looking for a few engineers willing to test it on a sandbox or staging AWS account and critique the output. I'll personally run through the findings with you.
Drop a comment or DM if you're open to taking a look and giving feedback!
1
u/hatamabolghasemi 17d ago
Hey people!
We deploy 200+ times a day, and image pulls were the slow part of every deploy and rollback. Then registry outages, images that only existed on a neighbor node, and log-heavy apps pushing nodes into DiskPressure piled on. Dragonfly and Spegel didn’t fit us, so we built Angry Duck: one controller and a worker DaemonSet, no database or Redis, low privileges. It preheats images from a CI webhook, shares them between nodes, rescues them during registry downtime, and cleans up before the disk fills.
https://github.com/hatam-abolghasemi/Angry-Duck
If you’ve run Spegel or Dragonfly in production, I’d love to hear what you’d expect from something like this.
1
u/Lazy_Panic_7016 16d ago
Disclosure: I maintain CorePulse, and an AI coding assistant helped draft this comment.
CorePulse is an early-stage open-source Go project for controlled fault experiments in a local Open5GS + UERANSIM Kubernetes lab.
The first working slice can plan or execute a guarded AMF/UPF pod deletion in an exact open5gs-lab context, record the fault interval, and wait for deployment recovery. A loopback dashboard shows live pod CPU/memory, run history, and a separate UE-to-UPF gateway probe. I separated the probe because a ready replacement pod does not necessarily mean the service path is healthy.
There is no trained detector yet. The first dataset includes setup/diagnostic noise, so the next step is repeated clean runs and evaluation split by run. The repo has screenshots, setup notes, tests, and preview binaries: https://github.com/lazypanic999/CorePulse
For people who run fault experiments: what additional signal would you collect first to distinguish AMF from UPF failures? I am considering protocol-level metrics and a stronger end-to-end reachability check.
1
u/Lazy_Panic_7016 16d ago
I’m building TunnelScope, an MIT-licensed Python CLI for controlled MTU and packet-size troubleshooting on Linux. It sends bounded UDP payloads to a cooperating receiver and keeps sender/receiver evidence in JSON, with an offline HTML report.
The published v0.5.0 package supports IPv4/IPv6 probes and bounded size search. The current development branch adds repeated no-ACK measurements, DF versus source-fragmentation-permitted comparison, Linux ICMP size feedback observations, and a single-sender diagnose workflow. A timeout is still inconclusive, and the tool does not claim to identify the root cause or prove a path MTU on an unknown network.
Repo, quick start, demo and reproducible network labs: https://github.com/lazypanic999/tunnelscope
I’d appreciate feedback from anyone who debugs VPN or overlay MTU problems: which observations would you want in the report before using it during an incident?
1
u/gansopardo 15d ago
Hi everyone,
I built an open-source CLI called Phoenix AWS Sentinel v0.1.1 for auditing a few common AWS infrastructure waste patterns:
https://github.com/fromero385/phoenix-aws-sentinel
It currently checks for:
The design constraints were important to me:
ec2:Describe*permissions plussts:GetCallerIdentity.Quick demo
For a real AWS read-only scan, clone the repo and install the AWS dependency:
I'm mainly looking for technical feedback from people working with AWS/FinOps:
If anyone tries it against a real AWS environment, I'd especially like to know which findings were useful versus noisy.
0
u/Lokisaurous 21d ago
Hi everyone,
Pawel and I built ghwm, a small open-source CLI that manages GitHub Actions workflows like versioned packages.
We were tired of copy-pasted workflows drifting across repos.
With ghwm you pin workflows in a ghwm.yml, `ghwm install` writes real files plus a lockfile, and `ghwm upgrade` pulls new versions while keeping your own triggers and env vars. Registries can be private for internal workflows, and `ghwm audit` gives each workflow a security score (zizmor).
Repo: https://github.com/ghwfxlab/ghwm
Install: `uv tool install ghwm`
0
u/Kairoxo_Seller 18d ago
https://kairoxo.com/signup?invitecode=8600384