@@ -112,3 +112,68 @@ Example commands to use are:
 - `mike deploy -p develop` - to deploy and push documentation for develop branch
 - `mike deploy -p -u v3.1.12 latest` - to deploy and push documentation for version v3.1.12 and update the `latest` alias to point to that version
 
+
+## Maintaining sponsors
+
+Public pages: `docs/sponsorship.md` (become a sponsor: tiers, routes, FAQ) and `docs/sponsors.md` (Our sponsors: the list).
+Permanent archive of sponsors: `SPONSORS.md` in the utPLSQL framework repository.
+
+### Onboarding a sponsor
+
+1. Receive logo and link. Accept SVG (preferred, with text converted to outlines), or a PNG with transparent background, tightly cropped, at least 256 px high or 768 px wide (2x the large box); 1152 x 384 px (3x) is ideal. Light/dark variants if needed. If only a lockup is supplied at the 64 px (small) size, ask for the wordmark or use the name as text.
+2. Store the logo in the `utPLSQL/.github` repository (the organization repository), in `.github/assets/sponsors/`, named `sponsor-<name>.png` or `sponsor-<name>.svg` (lowercase, hyphens; for light/dark variants `sponsor-<name>-light.svg` and `sponsor-<name>-dark.svg`). This follows the layout of the Material for MkDocs repository. All surfaces reference the file by its raw URL, `https://raw.githubusercontent.com/utPLSQL/.github/main/.github/assets/sponsors/sponsor-<name>.<ext>`. Do not hotlink the sponsor's own site.
+3. Add the entry to the matching grid in `docs/sponsors.md`. For 500 EUR and commercial sponsors also add it to the framework README, the organization profile README (`.github/profile/README.md`) and the landing page block in `docs/index.md` (marker `sponsors-landing`). 250 EUR sponsors: organization profile only.
+4. Add the name and start year to `SPONSORS.md`.
+5. 500 EUR and commercial sponsors: announce on LinkedIn, X and Bluesky.
+
+### Offboarding a sponsor
+
+1. At the end of the paid period plus 30 days, remove the logo from the framework README, the organization profile and the landing page.
+2. If the sponsor qualifies (3 months or a commercial agreement), move the entry to the Past sponsors grid in `docs/sponsors.md`. Otherwise delete it.
+3. Update `SPONSORS.md` (end year).
+
+Doing this by hand across four repositories drifts. Once there is a first paying sponsor, generate all blocks from one `sponsors.yml` (fields: name, url, logo, tier, start, end, status `current` or `past`) with a scheduled GitHub Action.
+
+### Sponsor lifecycle rules
+
+| State    | When                                                                                                                              | Where the sponsor appears                                                                                                                                              |
+|----------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Current  | from the first payment (GitHub Sponsors) or from receipt of the invoice payment (direct invoice) until the end of the paid period | per tier, see the recognition table in `docs/sponsorship.md`                                                                                                           |
+| Grace    | 30 days after the end of the paid period (failed card payments, late renewals)                                                    | unchanged                                                                                                                                                              |
+| Past     | after the grace period, only if the sponsor paid for at least 3 months, or had a commercial support agreement                     | `docs/sponsors.md` "Past sponsors" only, as a faded logo with no details. Removed from the GitHub organization profile, framework README and utplsql.org landing page. |
+| Lapsed   | after the grace period, sponsored for less than 3 months and no commercial agreement                                              | removed everywhere except the archive (`SPONSORS.md` in the utPLSQL  framework repository)                                                                                         |
+| Archive  | always                                                                                                                            | `SPONSORS.md`: name and year(s) only, kept permanently                                                                                                                 |
+
+Other rules:
+- A past sponsor is removed from the Past sponsors section on request, the same day. The archive entry is also removed if they ask.
+- Individuals are not listed on utplsql.org. GitHub shows public individual sponsors on the GitHub Sponsors page.
+- Release notes carry a link to `https://www.utplsql.org/sponsors.html`, never a list of names.
+- Commercial support never ends up in the recognition tiers by accident: someone who paid through GitHub gets recognition only, no support. Move them to a commercial agreement instead (see the channel separation in the sponsorship notes).
+- The user-facing wording of these rules is the FAQ "What happens when we stop sponsoring?" in `docs/sponsorship.md`. Change both together.
+
+### Presentation (`docs/sponsors.md`, styles in `docs/stylesheets/extra.css`)
+
+Every sponsor is a clickable logo (or a text link for 100 EUR sponsors) inside a grid. No tables. All organization tiers include a backlink to the sponsor's website: every logo and every name is a link to the URL supplied at onboarding, opened in a new tab with `rel="noopener sponsored"` (`sponsored` marks paid placements for search engines). In READMEs use a plain Markdown link.
+
+| Group              | Section on the page             | Grid class                         | Logo                                           |
+|--------------------|---------------------------------|------------------------------------|------------------------------------------------|
+| Commercial support | "Commercial support sponsors"   | `sponsor-grid sponsor-grid--large` | 128 px high, max 384 px wide (3:1), 32 px clear space |
+| 500 EUR            | "Organization sponsors", first  | `sponsor-grid sponsor-grid--large` | 128 px, as above |
+| 250 EUR            | "Organization sponsors", second | `sponsor-grid sponsor-grid--small` | 64 px high, max 192 px wide (3:1), 16 px clear space |
+| 100 EUR            | "Organization sponsors", last   | `sponsor-grid sponsor-grid--text`  | company name as a text link                    |
+| Past               | "Past sponsors"                 | `sponsor-grid sponsor-grid--past`  | 64 px high, max 192 px wide, grayscale, 55% opacity, logo only |
+
+Order inside a group: by start date, oldest first. Commercial support is listed above the recognition tiers.
+
+Entry format (one blank-line-separated item per sponsor; `markdown` attribute is required on the div):
+
+```html
+<div class="sponsor-grid sponsor-grid--large" markdown>
+[![Company name](https://raw.githubusercontent.com/utPLSQL/.github/main/.github/assets/sponsors/sponsor-company.svg)](https://company.example){ target=_blank rel="noopener sponsored" }
+</div>
+```
+
+For sponsors that supply separate light and dark logos, add two images with the classes `{ .logo-light }` and `{ .logo-dark }`.
+
+Put each group between its marker comments (`<!-- sponsors-commercial -->` ... `<!-- /sponsors-commercial -->`, `<!-- sponsors-organizations -->` ... `<!-- /sponsors-organizations -->`) and delete the "There are currently no ..." sentence when the first entry is added.
+
@@ -55,23 +55,6 @@ Many thanks to [all contributors](https://github.com/utPLSQL/utPLSQL/graphs/cont
 | Paul Walker                                        |                  |
 
 
-## Supporters
-
-utPLSQL is free and open source, built by its community. Sponsorships and other financial support are managed by utPLSQL Development Labs Ltd and fund dedicated maintenance and development of the project.
-
-Sponsorship does not provide ownership of utPLSQL or control over its direction.
-
-### Active supporters
-
-There are currently no active sponsors. If your company would like to support the project, comment on [this GitHub discussion](https://github.com/orgs/utPLSQL/discussions/22) or email [sponsors@utPLSQL.org](mailto:sponsors@utPLSQL.org).
-
-### Past supporters
-
-
-| Supporter                                                                                                                | Details                                                                |
-|--------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|
-| [![supported_by_redgate](assets/supported_by_redgate_100.png)](https://www.red-gate.com/hub/events/open-source-projects) | In 2019, Redgate supported utPLSQL by sponsoring stickers and t-shirts | 
-
 ## Contact
 
 For help with using utPLSQL, bug reports and feature ideas, please use [GitHub Discussions](https://github.com/orgs/utPLSQL/discussions).
 
@@ -0,0 +1,31 @@
+---
+layout: post
+title:  "utPLSQL is now open for sponsorship"
+date:
+  created: 2026-10-11
+categories:
+  - "news"
+description: "utPLSQL opens for sponsorship to help fund maintenance and development: organization tiers, commercial support and consulting."
+pin: true
+---
+
+In last months, we took steps to formalise utPLSQL and to give it a legal home under utPSLQL Development Labs Ltd. 
+With this being almost complete, it is now time to open utPLSQL for sponsorship that will allow for sustained development of this great framework.
+
+utPLSQL remains free to use and open source (Apache 2.0). 
+
+
+<!-- more -->
+
+Sponsorship is a way to collect funds required to allow for work on: and new features and support for new Oracle capabilities, compatibility updates, documentation, issue triage, hosting.
+
+## What is available
+
+- **Organization sponsorship** from 100 EUR / month, with recognition on utplsql.org, GitHub and the framework README
+- **Commercial support** with priority triage, a named contact and private consultation hours
+- **Consulting, training and problem-solving** for teams adopting or scaling utPLSQL
+- **Individual sponsorship** through GitHub Sponsors, any amount
+
+Sponsorship does not buy influence over the roadmap, and the project stays free for everyone.
+
+Details are on the [Sponsorship page](../../../sponsorship.md).
@@ -22,6 +22,7 @@
     { label: 'Documentation', url: BASE + '/documentation.html' },
     { label: 'Downloads',     url: BASE + '/downloads.html' },
     { label: 'Resources',     url: BASE + '/resources.html' },
+    { label: 'Sponsorship',   url: BASE + '/sponsors.html' },
     { label: 'About',         url: BASE + '/about.html' },
     { label: 'Contributing',  url: BASE + '/contributing.html' },
   ];
 
@@ -4,6 +4,7 @@ The utPLSQL project team welcomes contributions from the community.
 
 - **Contribute code** — please read the [contributing guide](https://github.com/utPLSQL/utPLSQL/blob/develop/CONTRIBUTING.md) before submitting a pull request.
 - **Ask questions and share ideas** — use [GitHub Discussions](https://github.com/orgs/utPLSQL/discussions) for support, questions, and feature proposals.
+- **Support the project** — [sponsorship](sponsors.md) funds maintenance and development.
 - **Report bugs and issues** — open an issue in the relevant [GitHub repository](index.md#frameworks-and-tools).
 
 The source code for all utPLSQL projects is hosted on the [utPLSQL GitHub organisation](https://github.com/utPLSQL).
@@ -22,6 +22,7 @@ Write and run tests directly in PL/SQL, integrate with your CI/CD pipeline, and
 
 - [Documentation](documentation.md) — installation, configuration, writing tests
 - [Downloads](downloads.md) — latest releases and changelogs
+- [Sponsorship](sponsors.md) — fund the maintenance and development of utPLSQL, or get commercial support
 
 ---
 
@@ -41,3 +42,12 @@ Write and run tests directly in PL/SQL, integrate with your CI/CD pipeline, and
 Have a question or idea? Start a [discussion on GitHub](https://github.com/orgs/utPLSQL/discussions) — it's the best place to ask for help, share feedback, or propose new features.
 
 utPLSQL is free and open source, built by its community and stewarded by [utPLSQL Development Labs Ltd](about.md#stewardship).
+
+---
+
+## Sponsors
+
+utPLSQL is free and open source (Apache 2.0). [Sponsorship](sponsors.md) funds development of new features and tools, maintaining compatibility with new Oracle versions and platforms, documentation.
+
+<!-- sponsors-landing -->
+<!-- /sponsors-landing -->
@@ -0,0 +1,35 @@
+---
+description: "The organizations and individuals who fund the maintenance and development of utPLSQL."
+---
+
+# Our sponsors
+
+utPLSQL is free and open source, built by its maintainers and contributors. Its maintenance and development are funded by the organizations and individuals listed here. Thank you.
+
+Sponsorship does not provide ownership of utPLSQL or control over its direction. Want to be listed?
+
+[Become a sponsor](sponsorship.md){ .md-button .md-button--primary }
+
+## Commercial support sponsors
+
+<!-- sponsors-commercial -->
+There are currently no commercial support sponsors.
+<!-- /sponsors-commercial -->
+
+## Organization sponsors
+
+<!-- sponsors-organizations -->
+There are currently no organization sponsors. If your company would like to support the project, see [Sponsorship](sponsorship.md) or email [sponsors@utPLSQL.org](mailto:sponsors@utPLSQL.org).
+<!-- /sponsors-organizations -->
+
+## Individual supporters
+
+Individuals who sponsor publicly are shown on the [utPLSQL GitHub Sponsors page](https://github.com/sponsors/utPLSQL).
+
+## Past sponsors
+
+<div class="sponsor-grid sponsor-grid--past" markdown>
+[![Redgate](https://raw.githubusercontent.com/utPLSQL/.github/main/.github/assets/sponsors/sponsor-redgate.png)](https://www.red-gate.com/hub/events/open-source-projects)
+</div>
+
+A complete list of all current and past sponsors is kept in [`SPONSORS.md`](https://github.com/utPLSQL/utPLSQL/blob/develop/SPONSORS.md) in the utPLSQL repository.