Integrations
Using Ulises Licenses with BuiltByBit
Sell Minecraft plugins on BuiltByBit and enforce licenses with Ulises Licenses. Learn what integrates, how buyer activation works, and what stays separate.
Ulises Licenses works alongside BuiltByBit sales: buyers check out on the marketplace while sellers issue Ulises license keys, verify them inside the plugin, and enforce HWID limits and revocation. Marketplace licenses are never imported; the two systems stay separate by design.
BuiltByBit is a premium marketplace for Minecraft resources where buyers check out and sellers distribute their work. Its terms allow sellers to protect resources with their own licensing and DRM systems, which is exactly where Ulises Licenses fits.
The integration is straightforward because responsibilities stay split: BuiltByBit handles discovery, checkout, and delivery of the purchase, while Ulises Licenses handles everything after (keys, verification, HWID binding, updates, and revocation).
Checkout stays on BuiltByBit
Buyers purchase normally through the marketplace. Nothing changes in your listing or their buying experience.
Keys issued per buyer
After each sale, generate a license key in the dashboard and deliver it to the buyer through BuiltByBit's established buyer communication.
Enforcement inside your plugin
Your plugin verifies the key with UlisesLib on every server it runs on, independent of where it was bought.
Updates and revocation
Ship new versions through Ulises auto-update with per-license watermarks, and revoke instantly on chargebacks or leaks.
How BuiltByBit Integration works
- 1
Sell as usual
List and sell your resource on BuiltByBit following their marketplace rules.
- 2
Issue the key
Create a license for the buyer in Ulises Licenses and deliver the key to them.
- 3
Buyer activates
The buyer puts the key in your plugin config. From then on, verification, HWID binding, and updates run through Ulises Licenses.
BuiltByBit Integration questions
Does this import my BuiltByBit licenses?
No. BuiltByBit licenses and Ulises licenses are separate systems. BuiltByBit records the purchase; Ulises Licenses enforces usage. There is no automatic sync between them.
Is external DRM allowed on BuiltByBit?
Marketplaces of this kind allow sellers to protect their resources with their own licensing systems. Always confirm against the current BuiltByBit terms before relying on this.
What happens on a refund or chargeback?
Revoke the Ulises license from your dashboard. The buyer keeps whatever BuiltByBit delivered, but the plugin stops working.
Without Ulises vs with Ulises
| Task | Manual | With Ulises |
|---|---|---|
| Issuing licenses | Copy-paste keys over DMs | Dashboard, bulk CSV, and Discord bot |
| Verification | None, or home-grown checks | Cloud API with signed responses |
| HWID and IP limits | Manual policing | Automatic enforcement with resets |
| Updates | Re-upload and re-share files | Auto-update with checksum verification |
| Leak tracing | No trail | Per-license watermarks |
| Revocation | Push a new build and hope | One click, effective on next check |
Related solutions
Java & Kotlin Licensing
Protect any JVM application with UlisesLib: Gradle and Maven setup, license verification, HWID binding, and automatic updates for Java and Kotlin software.
Minecraft Plugin Licensing
License protection for PaperMC and Spigot plugins with per-server HWID binding, IP limits, support-driven resets, watermarked downloads, and Discord management.
Polymart Integration
Sell Minecraft plugins on Polymart and enforce licenses with Ulises Licenses. Learn what integrates, how buyer activation works, and what stays separate.