Terms of Service
Effective: 17th of August 2026
These terms govern your use of the LaravelUi5 platform website at laravelui5.com ("Site") and your subscription to LaravelUi5 SDK ("the SDK"), both operated by Pragmatiqu IT GmbH ("we", "Pragmatiqu"), registered in Villach, Austria. By using the Site or completing SDK checkout, you accept these terms.
1. Definitions
- Site —
laravelui5.com, including all documentation, landing pages, and the blog content. - SDK — the LaravelUi5 SDK software, distributed via the private Composer repository at
packages.pragmatiqu.io. - Account — a free Pragmatiqu account, required to access gated documentation on the Site.
- Subscription — a paid LaravelUi5 SDK subscription, sold per the terms in sections 4 through 10.
- License year — the 12-month period starting from the date of purchase or renewal of an SDK subscription.
- Installation — a distinct deployment of an application built on the SDK, serving real users in production. An Installation may run on your own infrastructure, on infrastructure you rent, or on-premise at a customer's site, with or without a public domain name; all of these count the same. Installations, not domains, are the unit in which the SDK is licensed and counted.
- Production token — a Composer credential drawn for one specific Installation. Each Installation counts against the Installations included in your tier.
- Non-production token — a Composer credential used for development, testing, staging, continuous integration, or demonstration. Non-production tokens are included in every tier and are not counted.
- Rights holder — the entity that holds the intellectual property rights in the SDK from time to time, whether Pragmatiqu IT GmbH itself or an affiliated company. Every license granted in these Terms is granted with the rights holder's authority.
2. Account and Site access
OData documentation, the landing pages, the blog, and the journey content require no account.
To access gated documentation (Course), you must register an Account with a valid email address and verify it via the link we send you. You are responsible for maintaining the security of your Account credentials and for any activity that takes place under your Account.
Account registration is free and does not obligate you to subscribe to the SDK. You may close your Account at any time by writing to office@pragmatiqu.io.
3. Acceptable use of the Site
You agree to use the Site lawfully and in good faith. In particular, you agree not to:
- Attempt to gain unauthorized access to gated content, other Accounts, or the underlying infrastructure.
- Scrape, crawl, or otherwise systematically extract content beyond ordinary browser use.
- Interfere with the operation of the Site, including by automated load that exceeds reasonable individual use.
- Misrepresent your identity or your right to a tier of access you have not subscribed to.
We may suspend or terminate Site Accounts that materially breach these terms.
4. SDK subscription — Who can subscribe and how you sign up
LaravelUi5 SDK is sold exclusively to businesses (B2B): companies, agencies, freelancers acting in a commercial capacity, or other legal entities. By subscribing you confirm that you are acting on behalf of a business, not as a private consumer. EU consumer-protection rules specific to B2C purchases (including the unconditional 14-day withdrawal right) do not apply to B2B subscriptions.
Subscriptions are sold following a qualification call with us. Every new subscription begins with a Zoom conversation where we discuss your case, confirm fit, and answer questions. The onboarding link to self-service checkout is sent only after that call. This isn't a paywall trick; it's how we make sure you're getting what you actually need before you commit.
The qualification call doesn't create any obligation to purchase. If we determine the SDK isn't a good fit for your case during the call, we'll tell you so and recommend alternatives where we can.
5. SDK subscription — What you get
Your subscription grants:
- Access to the SDK Composer packages via
packages.pragmatiqu.io - Composer credentials, managed via your customer portal at
pragmatiqu.io/portal - Access to the gated documentation at
laravelui5.com/course/ - A license to use the SDK in your projects on the terms set out in § 8 (License grant).
Tier scope — Installations included, packages unlocked, optional add-ons — is shown at checkout and recorded on your license.
6. SDK subscription — Pricing and billing
- Subscriptions are billed annually in advance via our payment partner Paddle (Paddle.com Market Limited), who acts as Merchant of Record for your purchase.
- Prices are in EUR, exclusive of VAT. Paddle adds VAT at checkout based on your jurisdiction and remits it to the relevant authority.
- Subscriptions auto-renew at the end of each annual term at the then-current price unless cancelled. We notify you by email at least 14 days before each renewal.
- We do not offer multi-year discounts via self-service. For custom arrangements (volume, multi-year, agency and consultancy partnerships, OEM or embedded distribution), contact us directly during your qualification call or at
office@pragmatiqu.io.
7. SDK subscription — Cancellation and refund policy
7.1 Subscriptions are non-refundable
LaravelUi5 SDK subscriptions are sold to businesses (B2B) following a qualification call with us. Once you complete checkout, your payment is non-refundable. We do not offer a cooling-off period or pro-rated refunds for unused time.
This reflects the standard practice for annual B2B software subscriptions: when you buy a year, you commit to a year, and we commit to delivering it. The qualification call beforehand is what protects both sides. By the time you reach checkout, you and we have agreed the SDK fits your case.
7.2 You can cancel at any time
You may cancel your subscription at any time to stop future renewals. Cancel via:
- Your customer portal at
pragmatiqu.io/portal - Paddle's hosted portal (linked from your purchase confirmation email)
- Email to
office@pragmatiqu.io
Cancellations take effect immediately upon receipt:
- Auto-renewal stops. You will not be billed for the next term.
- Your access continues through the end of the current billed period ("grace period").
- After the grace period ends, your Composer credentials stop authenticating against
packages.pragmatiqu.io. Source code you have already installed via Composer remains usable on the Installations then licensed, under § 8.3 (After your subscription ends). - Your customer Account, license history, and audit records remain available for reactivation.
7.3 Goodwill exceptions
We retain discretion to issue refunds in exceptional circumstances, for example, demonstrable product malfunction on our side, billing errors, fraudulent account activity, or other situations where refusing a refund would clearly be unjust. These are case-by-case and are not a customer entitlement under these Terms. Contact office@pragmatiqu.io if you believe your situation qualifies and we'll work with you to find the right answer.
8. SDK subscription — License grant
The SDK is proprietary software. These Terms are the license; no public license text governs your use of the SDK source.
8.1 During your subscription
We grant you a non-exclusive, non-transferable license to install and use the SDK on the Installations included in your tier, for so long as your subscription is active. You may use the SDK in commercial production, for your own business, for your customers' projects, and in a product or service that you operate yourself.
An Installation is licensed wherever it runs. We do not distinguish by hosting model: your own servers, a cloud you rent, and an on-premise system at your customer's site are the same thing to us, and the SDK performs no license check at runtime and makes no outbound call.
Non-production use — development, testing, staging, continuous integration, demonstration — is included and is not counted, provided it runs on Non-production tokens and does not serve real users in production.
8.2 Restrictions
You may not:
- Redistribute, sublicense, or resell the SDK source, except as expressly permitted in § 8.5 (Delivering Installations to your customers).
- Remove or alter copyright, license, or authorship notices in the SDK source, or present the SDK itself as your own work. Branding the user interface of an application you deliver is a different thing and is expressly permitted — see § 8.5.
- Use the SDK to develop or operate a product or service that competes with Pragmatiqu's commercial offerings.
- Share your Composer credentials with third parties, except as expressly permitted in § 8.5.
- Run more Installations than your tier includes without licensing additional Installations.
8.3 After your subscription ends
The SDK version installed at the time your subscription ends remains licensed for use on the Installations then licensed, indefinitely. You will not receive updates, security patches, or new releases. You may not install or deploy the SDK in new Installations under the post-subscription license. The restrictions in § 8.2 continue to apply, as do the permissions in § 8.5 for the Installations you had already delivered.
This fallback license is part of what you pay for: a year of subscription buys both ongoing access to new releases and a permanent right to keep running what you installed during that year, on the Installations where you ran it. Where one of those Installations is operated by your customer, it keeps running too — they do not lose their system because you stopped subscribing. It does not survive termination for material breach (§ 9).
8.4 Continuity — if we stop
The SDK is proprietary, which means the code you run is maintained by one company. This section states what happens if that company stops maintaining it.
Trigger. The rights in this section become effective if either of the following occurs:
- insolvency proceedings are opened over the assets of Pragmatiqu IT GmbH or of the rights holder, or either of them ceases business; or
- ninety days pass after you report a critical defect to
office@pragmatiqu.iowithout both a security patch and a substantive written response from us.
A critical defect means a vulnerability in the SDK with a CVSS base score of 7.0 or higher, or a defect that prevents production operation of an installation that previously ran correctly.
What you may then do. You may modify the SDK version you are licensed to run, for the purpose of continued operation and security maintenance, on your own installations and on those of your customers under contracts existing at the time of the trigger. You may engage third parties to carry out that work on your behalf; they act for you and are bound by § 8.2 as you are.
What does not change. The restrictions in § 8.2, together with the permissions in § 8.5, continue to apply to you and to anyone acting for you. Beyond what § 8.5 already permits, this section does not grant the right to redistribute the SDK, to resell it as a product, or to use it in an offering that competes with Pragmatiqu's commercial offerings. Like the fallback license in § 8.3, it does not survive termination for material breach (§ 9).
Who this binds. This license is granted by Pragmatiqu IT GmbH with the authority of the rights holder, and binds both of them and their respective successors in title. A sale, assignment or intra-group transfer of the intellectual property rights in the SDK — including a transfer to an entity outside the European Union — does not affect licenses already granted under this section. Whoever holds the rights takes them subject to it.
Why there is no escrow agent. Source code escrow exists because on-premise software normally arrives as a compiled binary, so the source has to be deposited with a third party and released on a trigger. Composer distributes source: the SDK is already on your disk, in full, and it performs no license check at runtime and makes no outbound call. What this section adds is therefore not the code — you already hold it — but the right to change it. It is granted here, at the time you are licensed, rather than promised for a later date, so that it does not depend on us being in a position to keep promises.
This section applies to every SDK version you are licensed to run, including versions installed before it took effect.
8.5 Delivering Installations to your customers
Many of our customers do not run the SDK only for themselves. They build applications on it and hand them over to the businesses they serve. This section states what that permits, because § 8.2 read on its own would not.
You may deliver. You may build applications on the SDK and deliver them to your customers, including the SDK source as a Composer dependency of the application, and including Installations that your customer operates on their own infrastructure or on-premise. Each such Installation is one Installation under § 8.1 and counts against your tier.
You may use your own name. The application you deliver may carry your branding and your product name in its user interface. You are under no obligation to display ours. Copyright, license and authorship notices in the SDK source files stay as they are (§ 8.2); this permission covers what your users see, not what the source says.
The operator may hold the token. Where your customer operates the Installation, they may hold the Production token for that Installation, and their use of it for that Installation is not a breach of § 8.2. What they receive is the right to run the Installation you delivered. They do not receive a license to build new applications on the SDK, and § 8.2 binds them as it binds you. If they want to build their own, they need their own subscription.
What this does not permit. Selling the SDK as a product in its own right; offering it to third parties as a framework, library or development toolkit; or using it in an offering that competes with Pragmatiqu's commercial offerings. The line is between delivering an application that happens to be built on the SDK, which is what this section is for, and passing on the SDK itself, which it is not.
9. SDK subscription — Breach and termination
The restrictions in § 8.2 are the operative "you may not" list. We may suspend or terminate access for material breach of these Terms with written notice; remediable breaches receive a 14-day cure period before termination. Termination for cause ends the subscription, the post-subscription fallback license under § 8.3, the continuity rights under § 8.4, and your right to deliver further Installations under § 8.5, and does not entitle you to a refund.
Installations you had already delivered to a customer before termination, and that the customer operates, are not affected. Their right to run the application they were delivered survives your breach. We take this position deliberately: a dispute between us is between us, and a business that bought a working system from you should not lose it over it.
10. Service level and warranty
We provide the Site, the SDK, and supporting infrastructure (packages.pragmatiqu.io, the customer portal, the gated documentation) on a reasonable-effort basis. We do not guarantee specific uptime targets for self-service subscriptions; enterprise service-level agreements are available under separate written contract.
We provide technical support for active subscriptions by email (support@pragmatiqu.io) and through the customer portal, on business days (Central European Time). We aim to issue a first response within one business day for production-impacting issues and within two business days for other requests. These are response targets, not guarantees, and they cover the SDK as distributed — not your application code, infrastructure, or third-party software. We prioritise fixes by severity and our published roadmap and do not commit to resolution timeframes. Priority support with agreed response times is available to Platform customers under separate written contract. Full support terms are published at laravelui5.com/support.
To the maximum extent permitted by Austrian law, our total liability for any claim arising from your use of the Site or the SDK is limited to the amount you paid us in the twelve months immediately prior to the event giving rise to the claim. Liability for damages caused by gross negligence or willful misconduct is not limited where mandatory law prevents such limitation.
11. Privacy
Your data is handled per our Privacy Policy. We do not sell or share customer data beyond what is required to provide the service — payment processing (Paddle), email delivery (our email service provider), and infrastructure hosting (our hosting providers). The Privacy Policy lists the current data processors in detail.
12. Changes to these terms
We may update these Terms from time to time. Material changes apply to renewals and new subscriptions; your current billed period continues under the terms accepted at purchase. We notify you by email at least 30 days before material changes take effect. The current effective version is always available at the canonical URL listed in the footer of laravelui5.com.
13. Governing law and jurisdiction
These Terms are governed by the laws of Austria, excluding its conflict-of-laws rules and the UN Convention on Contracts for the International Sale of Goods (CISG). The competent court for any dispute arising out of or in connection with these Terms is the Landesgericht Klagenfurt, to the extent applicable law permits.
Pragmatiqu IT GmbH
Ribnigstraße 4, 9580 St. Niklas an der Drau
VAT ID — ATU80469039
office@pragmatiqu.io