Software Licensing Models

What do Access Advance's new royalty rates mean for video publishers, platforms, and the broader streaming ecosystem? I spoke with Peter Moller, CEO of Access Advance, and Dylan Zhou, SVP of Licensing, about the recently announced royalty structure for their video distribution patent pool. The discussion covered the codecs involved (VP9, AV1, HEVC, VVC), the tiered pricing model, waivers, and the list of initial licensors and licensees. We discussed not just the details, but the implications and finer points. How many companies will likely be impacted? Who qualifies for a waiver? What are the strategic implications for licensing in a multi-codec world? What's the new Royalty Adjustment Ladder? If you work in streaming, licensing, or codec deployment, you'll find the conversation useful and illuminating. https://lnkd.in/eragVUDi

If you're a service provider and Microsoft hasn't audited you yet, it's not because you're compliant. It's because it's not your turn yet. — SPLA audits will happen to every service provider eventually. The process is disruptive, time-consuming, confusing, and the results are always unexpected. — Most service providers underestimate their shortfalls by 80%. If you think your debt is $1 million, it's probably between $3 and $7 million. — We've defended over a hundred SPLA audits and are rarely wrong when we estimate shortfalls this way. — The most significant shortfalls relate to user licenses (SALs), accounting for 50-80% of total penalties on average. — Windows Server license shortfalls are the most difficult to mitigate during audit defense. — Microsoft appoints "independent auditors" from the Big Four: EY, PwC, KPMG, or Deloitte to verify your compliance. — SPLA stipulates that you'll pay 125% of list price for missing licenses. If non-compliance exceeds 5%, you'll cover all audit expenses too. What our experts recommend having learnt from 100+ audits: — Don't leave SPLA audit preparation to chance. The financial exposure is too severe for improvisation. — Start building robust historical data collection now. Every month you delay improvements, your debt to Microsoft grows. — Understand that this isn't a pleasant experience, but it's manageable with proper preparation and expert guidance. — Correct reporting mistakes immediately when you find them. Don't let them carry over to future periods. — Have emergency processes, tools, and trained personnel ready before the audit letter arrives. The question isn't if Microsoft will audit you, it's when. Are you ready? #microsoft #compliance #audit #samexpert

Top 5 Compliance Challenges Fintechs in the EMEA Region are Facing and How to Solve Them💡 If 2023 was the year of innovation and 2024 the year of consolidation, then 2025 is the year of compliance reckoning, the year when fintechs across the EMEA region realize that scaling fast without building strong regulatory foundations can no longer fly. Working in banking and regulatory compliance, I’ve seen how quickly regulatory expectations evolve, and this year, that gap between innovation and regulation will define who thrives and who struggles. Here are the five biggest compliance challenges fintechs are facing and how to get ahead of them: 1️⃣ Capital & Licensing Adequacy: Meeting minimum share capital requirements remains one of the biggest hurdles for fintech founders. Regulators in many jurisdictions now demand stronger proof of financial stability before granting licenses. Insufficient capital or poor funding structures often delay, if not derail, licensing applications entirely. 2️⃣ AI Governance & Model Risk Oversight: As AI becomes embedded in lending, fraud detection, and onboarding, regulators will intensify oversight of how models are designed, tested, and monitored. Expect stricter demands around data ethics, explainability, and accountability, particularly for “black box” algorithms and automated decision-making systems. 3️⃣ AML & Data Localization Pressures: With stronger AML regimes and growing data localization requirements, fintechs will need to rethink how they collect, store, and manage customer information. Weak data governance can expose companies to regulatory penalties and erode customer trust, a risk few can afford this year. 4️⃣ Ongoing Reporting & Recordkeeping Obligations: Compliance doesn’t end after licensing. Fintechs face continuous reporting, transaction monitoring, and audit obligations, especially under heavy frameworks like MiCA in the EU. Those operating in multiple jurisdictions must prepare for varying, and often overlapping, reporting timelines and requirements. 5️⃣ Customer Data Protection & Trust Building: Handling sensitive financial data comes with immense responsibility. Weak cybersecurity or poor data protection frameworks can cause not only regulatory breaches but long-term reputational damage. Fintechs that embed privacy and trust at the heart of their operations will have a distinct competitive advantage. Ultimately, compliance will no longer be a box-ticking exercise;  it will become a strategic differentiator. Like I always say, the fintechs that thrive will be those that treat compliance as a core part of their business model, not an afterthought. 💡Question for fintech leaders: How prepared is your organisation for these shifts? Are your teams building compliance into your innovation roadmap or catching up only when regulators call? #ComplianceWithTomi #Fintech #Regulation #Banking #EMEA #RiskManagement #AI #FintechAfrica #FinancialRegulation

Individual vs. Corporate Sales Nav Licenses: Data Integrity at Stake Sales leaders, here’s one of the critical reasons to invest in corporate Sales Navigator licenses: Data integrity. At Google, they drilled into us: data is king. And when it comes to Sales Nav, the way your team is licensed directly impacts who owns that data. If your reps are on individual licenses, all their saved leads, accounts, and messages leave with them when they exit the company. Poof. Gone. With a corporate license, that data stays with your org and can be reassigned to a new team member, thereby keeping your pipeline intact and your momentum going. And the headaches don’t stop at data loss. If your company is paying for individual licenses on a corporate card, you risk: - Ongoing charges after an employee's departure, especially if subscriptions aren't promptly canceled - Administrative overhead from managing reimbursements and tracking usage - Limited visibility into team-wide usage and ROI, hindering performance assessments If you want control, continuity, and cleaner ops, invest in a corporate package. It’s not just a software decision. It’s a strategy move. #salesnavigator #dataisking #dataintegrity

🌏 𝗧𝗵𝗲 𝗦𝗶𝗹𝗲𝗻𝘁 𝗗𝗲𝗮𝗹 𝗕𝗿𝗲𝗮𝗸𝗲𝗿 𝗶𝗻 𝗦𝗼𝘂𝘁𝗵𝗲𝗮𝘀𝘁 𝗔𝘀𝗶𝗮: 𝗥𝗲𝗴𝘂𝗹𝗮𝘁𝗼𝗿𝘆 𝗦𝘂𝗿𝗽𝗿𝗶𝘀𝗲𝘀 Expanding into Southeast Asia? You’ve done your market research, built local connections, and even lined up potential clients. But then—a sudden licensing requirement, a change in foreign ownership rules, or an unexpected tax compliance issue throws everything off course. Sound familiar? You’re not alone. 𝗥𝗲𝗴𝘂𝗹𝗮𝘁𝗼𝗿𝘆 𝘀𝘂𝗿𝗽𝗿𝗶𝘀𝗲𝘀 𝗮𝗿𝗲 𝗼𝗻𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 (𝗮𝗻𝗱 𝗺𝗼𝘀𝘁 𝘂𝗻𝗱𝗲𝗿𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲𝗱) 𝗿𝗶𝘀𝗸𝘀 𝗳𝗼𝗿 𝗳𝗼𝗿𝗲𝗶𝗴𝗻 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝗲𝗻𝘁𝗲𝗿𝗶𝗻𝗴 𝗔𝗦𝗘𝗔𝗡. Why? Because: 🔴 𝗥𝘂𝗹𝗲𝘀 𝗰𝗵𝗮𝗻𝗴𝗲—𝗼𝗳𝘁𝗲𝗻. Governments across the region frequently update policies to attract investment, protect local industries, or adapt to global trends. What was compliant last year may not be today. 🔴 𝗘𝘃𝗲𝗿𝘆 𝗺𝗮𝗿𝗸𝗲𝘁 𝗶𝘀 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁. Singapore’s transparent and structured system is worlds apart from Indonesia’s layered bureaucracy or Vietnam’s evolving regulations. A one-size-fits-all compliance approach simply doesn’t work. 🔴 𝗨𝗻𝘄𝗿𝗶𝘁𝘁𝗲𝗻 𝗿𝘂𝗹𝗲𝘀 𝗺𝗮𝘁𝘁𝗲𝗿. In many markets, 𝗵𝗼𝘄 you navigate regulations is just as important as 𝘄𝗵𝗮𝘁 the regulations state. Relationships with local authorities, understanding procedural nuances, and knowing the right timelines can make all the difference. ✅ 𝗛𝗼𝘄 𝘁𝗼 𝗦𝘁𝗮𝘆 𝗔𝗵𝗲𝗮𝗱 𝗼𝗳 𝗥𝗲𝗴𝘂𝗹𝗮𝘁𝗼𝗿𝘆 𝗥𝗶𝘀𝗸 𝗶𝗻 𝗔𝗦𝗘𝗔𝗡 1️⃣ 𝗗𝗼𝗻’𝘁 𝗿𝗲𝗹𝘆 𝗼𝗻 𝗼𝘂𝘁𝗱𝗮𝘁𝗲𝗱 𝗽𝗹𝗮𝘆𝗯𝗼𝗼𝗸𝘀. What worked in one market—or even last year—may no longer be valid. Stay proactive in monitoring changes. 2️⃣ 𝗘𝗻𝗴𝗮𝗴𝗲 𝗹𝗼𝗰𝗮𝗹 𝗲𝘅𝗽𝗲𝗿𝘁𝗶𝘀𝗲 𝗲𝗮𝗿𝗹𝘆. A good local partner or advisory team isn’t just useful—they’re essential. They help you avoid costly missteps before they happen. 3️⃣ 𝗣𝗹𝗮𝗻 𝗳𝗼𝗿 𝗰𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝗰𝗲 𝗳𝗿𝗼𝗺 𝗗𝗮𝘆 𝟭. Some companies wait until they’re hit with a regulatory issue before taking compliance seriously. The smart ones integrate it into their strategy from the start—ensuring smoother operations and avoiding legal headaches. 🚀 𝗧𝗵𝗲 𝗼𝗽𝗽𝗼𝗿𝘁𝘂𝗻𝗶𝘁𝘆 𝗶𝗻 𝗦𝗼𝘂𝘁𝗵𝗲𝗮𝘀𝘁 𝗔𝘀𝗶𝗮 𝗶𝘀 𝗺𝗮𝘀𝘀𝗶𝘃𝗲, 𝗯𝘂𝘁 𝗼𝗻𝗹𝘆 𝗳𝗼𝗿 𝘁𝗵𝗼𝘀𝗲 𝘄𝗵𝗼 𝗽𝗹𝗮𝘆 𝗯𝘆 𝘁𝗵𝗲 𝗿𝘂𝗹𝗲𝘀 (𝗮𝗻𝗱 𝗸𝗻𝗼𝘄 𝘄𝗵𝗲𝗻 𝘁𝗵𝗲 𝗿𝘂𝗹𝗲𝘀 𝗮𝗿𝗲 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴). Have you faced regulatory surprises in the region? Would love to hear your experiences in the comments!

State compliance is the hidden challenge every fintech founder needs to know about. Not even bank sponsorship gets you out of it. Here's what no one tells you about state-level compliance in lending: There are only 2 ways to legally originate loans: • State lending licenses  • Partner banks But here's the kicker - even with a bank partner, you STILL need state registrations. Depending on the states you are lending in and servicing, states require you to get licenses. Most founders miss this completely. We did too. At my company, we had to register in 25 states and went through 10+ comprehensive audits. Here's what's really happening behind the scenes: Every state requires 3 things: • Registration & licensing • Regular reporting (monthly to annually) • Comprehensive audits The registration process is brutal: • Need specific license types • Surety bonds required • Minimum balance requirements • Full financials for every 10%+ owner • Mountains of paperwork But getting the license is just the beginning. The real work? Maintaining it: • Monthly/quarterly/annual reports • Different formats for each state • Custom calculation methods • Team-wide coordination needed • Personal attestation required Then come the audits: • Some states audit yearly • They check EVERYTHING • Marketing materials • Customer communications • Payment reconciliation • Regulation compliance Think you can handle this with a small team? Think again: • Need compliance experts • Legal support required • Engineering involvement • Product team coordination • Back office operations • External consultants Bank sponsorship helps, but doesn't eliminate the work. The reality? • Regulations change constantly • Each change impacts multiple teams • Implementation deadlines are strict • Documentation must be accurate My advice to fintech founders: Build compliance muscle early. Work with experienced partners. Budget for the hidden costs. This isn't just about checking boxes. It's about building a sustainable fintech business that can scale. Read the full post. Link in comments.

(DAY-5): Common Oracle Licensing Pitfalls to Avoid Oracle Licensing is complex, and even minor mistakes can lead to significant compliance issues or unexpected costs. Today, let’s explore the most common pitfalls organizations face and how to avoid them. --- 1. Misinterpreting Licensing Metrics Using the wrong metric (e.g., NUP vs. Processor) can lead to non-compliance. Always confirm which metric applies to your deployment and ensure correct calculations. Example: Deploying Oracle Database Enterprise Edition on a multi-core server requires precise calculations using the Core Factor Table. --- 2. Overlooking Virtualization Rules Oracle’s policies often require licensing all physical cores in virtualized environments, even if only a portion is used. Many organizations assume virtual machines can be licensed independently, leading to under-licensing. Pro Tip: Review Oracle’s Partitioning Policy to understand how virtualization affects licensing. --- 3. Ignoring License Mobility and Cloud Rules Migrating from on-premise to cloud or hybrid setups without understanding license mobility policies can cause compliance gaps. Example: Licenses purchased for on-premise may not automatically transfer to Oracle Cloud Infrastructure (OCI). Always verify mobility options. --- 4. Inadequate User Tracking For NUP licenses, organizations often fail to monitor and document the actual number of users. Even inactive accounts can trigger compliance issues during audits. Solution: Regularly audit user accounts and align them with your licensing agreements. --- 5. Underestimating Audit Preparation Oracle conducts audits frequently, and lack of preparation can result in hefty penalties. Best Practices: • Maintain accurate usage records. • Regularly review contracts for updates. • Engage experts to simulate audits and identify gaps. --- 6. Misjudging Licensing Needs for Test/Dev Environments Test or development environments are often overlooked, leading to unlicensed deployments. Fact: Oracle requires full licensing even for non-production environments unless explicitly stated otherwise. --- 7. Not Leveraging Support and Updates Failing to keep up with annual support renewals can restrict access to critical updates and patches, creating security risks. Tip: Build support renewals into your budget to maintain software health and compliance. --- 8. Assuming "Free" Software is Always Free Oracle offers free editions like Oracle Database XE, but expanding beyond its limitations requires proper licensing. Example: Moving from XE to a full edition without licensing triggers compliance risks. --- Stay tuned for Day-6! Tomorrow, we’ll deep dive into "Preparing for Oracle License Audits" to explore practical solutions and best practices to stay ahead of compliance challenges. What challenges have you faced with Oracle Licensing? Let’s discuss in the comments below! #OracleLicensing #ITCompliance #SoftwareAssetManagement

How much does a virtual asset license really cost?   Application fees are only one part of the total cost.   Beyond licensing fees, here are other costs you need to budget for:    ↳ Regulator Supervision Fees - Annual fees required to maintain your license   ↳ Commercial Entity Set Up Costs - Application, Registration, Company license, Certificate of incorporation, etc.   ↳ Banking & Insurance - Client money account setup and VASP insurance   ↳ Compliance & AML Requirements - Systems, audits, and reporting to meet UAE regulations   ↳ Talent & Operational Setup - Hiring compliance officers, setting up offices, and training staff    Each regulator (VARA, ADGM, DIFC) has different cost structures, and the total expenses can add up quickly.   Use the comparison table below to get a clearer picture of licensing fees.   If you want a full breakdown of costs - and how to avoid unexpected expenses - let’s talk.

Rationale behind Finland’s gambling supervisory fee Finland introduces a partial gambling licensing system and licensed operators may commence their operations at the beginning of 2027. System includes an annual supervision fee ranging from B2B’s fixed 1,500€ to B2C’s 4,000€ - 434,000€, depending on GGR. The rationale of the supervision fee is to ensure sustainable and independent regulatory oversight of the gambling market. The key rationales include: 🔹 Cost recovery The fee is designed to fully cover the budgeted costs of gambling supervision, including staffing, IT systems, and enforcement activities. This aligns with principles applied in other regulated sectors like financial supervision. 🔹 Proportionality and fairness Fees vary based on license type, business size, and game vertical. This ensures fairness—larger operators or more supervision-intensive activities (e.g., physical slot machines) are charged more. 🔹 Predictability and budgetary alignment The annual amount is capped and aligned with actual budget needs. Any significant over-collection (beyond 5% of the authority’s budget) must result in reduced fees for licensees the following year. 🔹 Two-part fee for new operators In the first year of operation, a base fee is charged upfront and adjusted retroactively based on actual gross gaming revenue (GGR). This avoids unfair burden for newcomers without operating history. 🔹 Transparency and legal certainty The fee structure and its calculation are clearly defined in the law, and operators are informed in advance. Payment schedules can be flexible, and public oversight is ensured What do you think of Finland’s supervision fee model and its rationale? Is it a reasonable solution or an entry barrier? How should the fee be adjusted over time? ------------------------------------------- Hi. I'm Antti Koivula — iGaming lawyer and Finnish iGaming market expert at Legal Gaming Attorneys at Law. Follow me for insights on regulation, compliance, and the future of iGaming in Finland. You can reach me through email at antti@legal-gaming.com.  

Here's a somewhat controversial opinion: on-prem, perpetual licenses won't become obsolete because of cloud or SaaS alternatives. While SaaS and Cloud models offer unparalleled flexibility for user-based licenses — allowing companies to scale up or down instantly and stop costs with the click of a button — the conversation shifts when we look at enterprise server software. (Btw, if you think old-school license management is complex, try FinOps). For enterprise systems with a long-term operational horizon, on-prem perpetual licenses still present the most compelling value proposition. On-prem perpetual licenses may involve higher upfront costs, but for systems intended to sustain production for many years, they become significantly more cost-effective. The total cost of ownership decreases over time, making it an ideal choice for established systems where usage patterns are predictable and consistent. On-prem licenses offer complete control over the IT environment, which is crucial for companies with stringent data security, compliance, and governance requirements. This control extends to the software lifecycle, allowing businesses to plan upgrades, downgrades, step-ups, and changes on their terms. For organizations with BYOL agreements, the flexibility to transfer existing licenses to new hardware or cloud-based environments combines the best of both worlds—on-premises control with the scalability of cloud computing. SaaS models have undoubtedly transformed how businesses access and use software, catering to the need for flexibility and scalability in dynamic environments. However, when it comes to enterprise server software, where long-term stability and control are paramount, on-prem perpetual licenses stand out as a better strategic choice. They are not just about cost-saving but about aligning IT infrastructure with business strategy for sustained success. As Ryan Bendana pointed out (link in the comments), don't let sales double-talk confuse you by referring to "perpetual licenses" as "on-premise" licenses to get you into the cloud and help them meet their quota.