Release Repository FAQ

How JagREPO delivers private software updates.

These answers explain the customer flow from app update checks through release publishing, download tracking, private file delivery, and CI/CD automation.

Core product questions

The SaaS flow is designed around private update manifests, tracked downloads, and release publishing automation.

How does my app check for updates?

Your app, installer, CLI, WordPress plugin, or web script checks the JagREPO update endpoint assigned to that product. JagREPO compares the installed version to the published release channel and responds with either no update or the release details your app needs to continue.

The exact setup snippet is generated inside the customer dashboard after the product is created.

Release files reside here on JagREPO. Each product keeps the release details needed to serve the correct build for its version, channel, platform, and architecture.

No. Customers manage products, releases, versions, platforms, and package limits inside JagREPO. JagREPO handles private repository delivery behind the scenes.

JagREPO tracks repository activity such as update checks, release downloads, uploads, usage totals, platforms, versions, package limits, checksums, and audit events. This gives customers billing visibility and gives admins support visibility.

Create a product API token in your dashboard, store it as a masked CI/CD variable, then have GitLab, GitHub Actions, or a local build script create the release, upload the artifact, and publish it through JagREPO.

JagREPO is being expanded from WordPress themes and plugins into a broader update repository for EXE, MSI, DMG, PKG, DEB, RPM, AppImage, ZIP, TAR.GZ, CLI tools, web scripts, private repositories, and custom software artifacts.

Additional support questions

These are the active FAQ entries managed by the JagREPO admin team.

What is JagREPO for?
It's for the premium plugin and theme developers for WordPress. Which in turns allows a developer of either type to add two lines of code, a simple class file to their plugin/theme. Give to their end-user, and do all of their version control here at JagRepo.
YES! This is for the life of this account! This is to help the struggling developer of a plugin/theme to get started. We do NOT ask you to upgrade unless you need more plugin/theme space. :) Enjoy from the bottom of our developer's hearts at Jag Journey, LLC!
Of course, this is totally up to you and how you would want to do this, just make sure you have permission from this person/company beforehand. We are not held responsible for who has your plugin/theme.
Absolutely not, we are NOT a directory here. We're a SaaS, and protect our client's privacy and IP work to the fullest, and do NOT share this with anyone! Not even the President of the United States would get to know!
The actual owner that's listed on the product that you purchased/received it from is the best answer. We do NOT own any of the plugins/themes within JagREPO! We're a simple automatic service provider for WordPress theme+plugin developers. The owners that upload them here are the 100% owner of their own products they choose to host here under our JagREPO.
It simply means the following:

Jag = Jag Journey, LLC Brand Name
Repo = Repository which in turn is in reference to versioning control, allowing developers of themes and plugins to house their versions here and create a full changelog along the way.
Sure you can, it's free and we do NOT need your information for billing, you will provide that securely here on JagREPO.com make sure there's an https:// before you do any purchasing. 

Signup here: JagREPO Signup
  • First, you need to be signed in.
  • Next, then you visit the Pricing page.
  • Pick the package that best suits your needs.
  • Enjoy and done!
Yes, you're in control of what server (IP Address) connects to and downloads your product(s)!
Absolutely NOT! We're just here to be your automatic update provider for your plugin/theme!