[Skip to content](#main)

[→](/)

[![Avunu](/brand/avunu-logo.svg)![Avunu](/brand/avunu-logo-light.svg)](/)[Services](/services/)[Consulting](/services/consulting/)[ERP](/services/erp/)[Odoo](/services/erp/odoo/)[ERPNext](/services/erp/erpnext/)[Custom software](/services/custom-software/)[Devices & IoT](/services/devices-iot/)[Websites](/services/websites/)[Infrastructure](/services/infrastructure/)[Partners](/partners/)

[Work](/work/)[Open source](/open-source/)[Knowledge base](/kb/)[About](/about/)

[About Avunu](/about/)[Team](/about/team/)[Insights](/insights/)[Contact](/contact/)

[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

- [Services](/services/)[Consulting](/services/consulting/)
- [ERP](/services/erp/)
- [Odoo](/services/erp/odoo/)
- [ERPNext](/services/erp/erpnext/)
- [Custom software](/services/custom-software/)
- [Devices & IoT](/services/devices-iot/)
- [Websites](/services/websites/)
- [Infrastructure](/services/infrastructure/)
- [Partners](/partners/)

[Work](/work/)[Open source](/open-source/)[Knowledge base](/kb/)[About](/about/)

- [About Avunu](/about/)
- [Team](/about/team/)
- [Insights](/insights/)
- [Contact](/contact/)

[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

[Knowledge base](/kb/)[NixOS](/kb/nixos/)WordPress performance and hardening on Nix

Search the knowledge basePress/

ESC

Jump to

[Browse the knowledge base](/kb/)[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[Odoo](/kb/odoo/)[WordPress](/kb/wordpress/)[NixOS](/kb/nixos/)[Email](/kb/email/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

↵select↑↓navigateescclose

Search the knowledge base

[Skip to the article](#kb-article)[NixOS](/kb/nixos/)13 articles

- [Overview](/kb/nixos/)
- [A NixOS micro desktop for family and friends](/kb/nixos/nixos-micro-desktop-for-family-and-friends/)
- [Add OCA modules to an odoo-nix project](/kb/nixos/adding-oca-modules-with-odoo-nix/)
- [Build a Firefox web kiosk USB drive with web_kiosk](/kb/nixos/building-a-web-kiosk-usb-with-web-kiosk/)
- [Build production images with frappe-nix](/kb/nixos/building-production-images-with-frappe-nix/)
- [Mount and sync cloud storage on NixOS with nixos-rclone](/kb/nixos/mounting-cloud-storage-with-nixos-rclone/)
- [Reference architecture for self-hosting business systems on NixOS](/kb/nixos/reference-architecture-for-self-hosting-business-systems/)
- [Run Frappe as a NixOS service](/kb/nixos/running-frappe-as-a-nixos-service/)
- [Run Odoo as a NixOS service](/kb/nixos/running-odoo-as-a-nixos-service/)
- [Run WordPress on FrankenPHP with wordpress-nix](/kb/nixos/wordpress-on-frankenphp-with-wordpress-nix/)
- [Set up a reproducible Frappe development environment with frappe-nix](/kb/nixos/frappe-dev-environment-with-frappe-nix/)
- [Set up an Odoo and OCA development environment with odoo-nix](/kb/nixos/odoo-dev-environment-with-odoo-nix/)
- [Why Nix for business systems](/kb/nixos/why-nix-for-business-systems/)
- [WordPress performance and hardening on Nix](/kb/nixos/wordpress-performance-and-hardening-on-nix/)

Other sections[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[Odoo](/kb/odoo/)[WordPress](/kb/wordpress/)[Email](/kb/email/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

In NixOS: 13 articles

[Overview](/kb/nixos/)[A NixOS micro desktop for family and friends](/kb/nixos/nixos-micro-desktop-for-family-and-friends/)[Add OCA modules to an odoo-nix project](/kb/nixos/adding-oca-modules-with-odoo-nix/)[Build a Firefox web kiosk USB drive with web_kiosk](/kb/nixos/building-a-web-kiosk-usb-with-web-kiosk/)[Build production images with frappe-nix](/kb/nixos/building-production-images-with-frappe-nix/)[Mount and sync cloud storage on NixOS with nixos-rclone](/kb/nixos/mounting-cloud-storage-with-nixos-rclone/)[Reference architecture for self-hosting business systems on NixOS](/kb/nixos/reference-architecture-for-self-hosting-business-systems/)[Run Frappe as a NixOS service](/kb/nixos/running-frappe-as-a-nixos-service/)[Run Odoo as a NixOS service](/kb/nixos/running-odoo-as-a-nixos-service/)[Run WordPress on FrankenPHP with wordpress-nix](/kb/nixos/wordpress-on-frankenphp-with-wordpress-nix/)[Set up a reproducible Frappe development environment with frappe-nix](/kb/nixos/frappe-dev-environment-with-frappe-nix/)[Set up an Odoo and OCA development environment with odoo-nix](/kb/nixos/odoo-dev-environment-with-odoo-nix/)[Why Nix for business systems](/kb/nixos/why-nix-for-business-systems/)[WordPress performance and hardening on Nix](/kb/nixos/wordpress-performance-and-hardening-on-nix/)

Other sections[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[Odoo](/kb/odoo/)[WordPress](/kb/wordpress/)[Email](/kb/email/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

NixOSWordPress performance and hardening on Nix

What the platform mu-plugins do for speed and security on SQLite-backed WordPress sites, and how to audit a MySQL dump before you restore it.

UpdatedOct 5, 2026

Applies towordpress-nix (main branchOctober 2026)wordpress-sqlite-anywhere 1.2 or later for the performance keys

Tagsnixoswordpressperformancesecurity

Reading time12 min

On this page[How the platform plugins are delivered](#how-the-platform-plugins-are-delivered)[Performance keys for SQLite engines](#performance-keys-for-sqlite-engines)[How and when the keys are added](#how-and-when-the-keys-are-added)[The hardening mu-plugins](#the-hardening-mu-plugins)[Page cache and the two planes](#page-cache-and-the-two-planes)[The edge cache](#the-edge-cache)[Purging](#purging)[What the public plane refuses](#what-the-public-plane-refuses)[User enumeration protection](#user-enumeration-protection)[Audit a dump before you restore it](#audit-a-dump-before-you-restore-it)[Strip the executable objects](#strip-the-executable-objects)[Limits to know about](#limits-to-know-about)[Related documents](#related-documents)

The wordpress-nix platform ships a set of must-use plugins (mu-plugins) that tune the database, harden the public surface, and cooperate with an edge page cache, so a site needs no plugin for any of it. Use it alongside [WordPress on FrankenPHP with wordpress-nix](/kb/nixos/wordpress-on-frankenphp-with-wordpress-nix/). Read it when you want to know what those files do, what they assume, and how to vet a MySQL dump from a host you do not control before you migrate it.

## How the platform plugins are delivered

The files live in `mu-plugins/` in the platform repository and are named `platform-*.php`. On every deploy the platform copies the current `platform-*.php` files into the site's `wp-content/mu-plugins/`, replacing the old copies. Anything else in that directory is left alone. Git mode is the exception. It serves a read-only tree that you provide, so build that tree with `lib.mkSiteDocroot`, which includes the platform mu-plugins (see [WordPress on FrankenPHP with wordpress-nix](/kb/nixos/wordpress-on-frankenphp-with-wordpress-nix/)).

That has one practical consequence: do not edit a `platform-*.php` file inside a site. Your change is overwritten on the next deploy. If you need different behavior, change it in the platform and let every site pick it up through a flake input bump.

## Performance keys for SQLite engines

`platform-performance-keys.php` adds composite indexes to the core meta and posts tables when a site runs on one of the platform's SQLite-backed engines (a local file, Turso, or D1). It is the SQLite counterpart of what the [Index WP MySQL For Speed](https://wordpress.org/plugins/index-wp-mysql-for-speed/) plugin does on MySQL.

WordPress ships single-column keys on the meta tables: `meta_key` alone and the object id alone. A query that joins on both, such as a `meta_query` on the front page, has to scan one side. A composite key fixes that. The platform adds these:

| Table         | Key name                  | Columns                                          |
| ------------- | ------------------------- | ------------------------------------------------ |
| `postmeta`    | `meta_key_post_id`        | `meta_key(191), post_id`                         |
| `usermeta`    | `meta_key_user_id`        | `meta_key(191), user_id`                         |
| `termmeta`    | `meta_key_term_id`        | `meta_key(191), term_id`                         |
| `commentmeta` | `meta_key_comment_id`     | `meta_key(191), comment_id`                      |
| `posts`       | `post_parent_type_status` | `post_parent, post_type, post_status`            |
| `posts`       | `author_type_status_date` | `post_author, post_type, post_status, post_date` |

The repository records one measurement: a front-page `meta_query` on the first migrated site dropped from 600 ms to under 80 ms once the `postmeta` key was in place. Treat that as one query on one site, not a promise. The platform's own notes quote two figures for it (37 ms in the source comment, 77 ms in the README), so the safe reading is "from 600 ms to well under 100 ms".

The plugin deliberately does not copy the MySQL plugin's central trick of making the composite key the clustered primary key. SQLite clusters a table by `rowid`, so there is no equivalent, and those rewritten primary keys are exactly what `restore-core-keys` has to undo during a migration.

### How and when the keys are added

The keys are created with `ALTER TABLE ... ADD KEY` through the database driver, never with a raw `CREATE INDEX`. That way the driver's emulated information schema knows about them and a later table rebuild keeps them.

It runs on the admin plane only (`admin_init`, and during cron), because the public plane never writes.

It records the applied version in the `platform_performance_keys` option, so it does the work once. A key that already exists is skipped, and a "Duplicate key name" answer from the primary counts as success.

If any key fails, the plugin writes a line to the PHP error log and leaves the option unset, so it tries again on the next admin request.

Note

The feature switches itself off on MySQL, and on any SQLite driver that cannot add an index in place. In practice that means wordpress-sqlite-anywhere 1.2 or later. On an older driver, `ALTER TABLE` rebuilds the whole table, which on Turso means copying `wp_postmeta` through a very slow insert path.

To confirm it ran, check the option from the service user:

```
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">sudo</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">-u</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">wordpress</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">wp</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">option</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">get</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">platform_performance_keys</span>
```

It reads `1` once the keys are applied. This document does not verify the output of a live `SHOW INDEX` against a running site, so use that as a second check if you need one.

## The hardening mu-plugins

Each file does one job. These are the ones that matter for security and request handling.

| File                                 | What it does                                                                                                                                                             |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `platform-user-enumeration.php`      | Stops anonymous visitors from discovering usernames. Details in the next section.                                                                                        |
| `platform-public-plane.php`          | On the public half of a split-plane site, refuses to authenticate any user who can `edit_posts`, disables XML-RPC, and hides the admin bar.                              |
| `platform-admin-plane.php`           | On the admin half, moves post preview links from the public host back onto the admin host so editors can actually preview.                                               |
| `platform-environment.php`           | Drops listed plugins from `active_plugins` at load time, without touching the database. Used for production-only plugins in a dev shell, and for plane-specific plugins. |
| `platform-nonce.php`                 | Raises the `nonce_life` filter to 60 days.                                                                                                                               |
| `platform-cloudflare-page-cache.php` | Signals cacheability to the edge cache and purges it on content changes. See the page cache section.                                                                     |
| `platform-gitium.php`                | Activates the platform's own copy of gitium by filter, so the site repository never records it as active.                                                                |

Warning

`platform-nonce.php` stretches WordPress nonces far beyond their default lifetime of one day. Nonces are a defense against cross-site request forgery, so a longer life widens the window in which a captured one stays valid. Know that you are carrying this trade before you rely on it, and change the platform file if your threat model needs the default back.

## Page cache and the two planes

A site can run as two instances on one shared database: a public plane on the real hostname that never serves an administration surface, and a private admin plane behind an identity proxy. The page cache sits in front of the public plane.

### The edge cache

The platform's Cloudflare Worker caches anonymous HTML pages, so a hit never reaches PHP or the database. The Worker only stores a response when all of these hold:

The request is a `GET` (or `HEAD` for lookup) with no WordPress login, post-password, comment-author or WooCommerce cart cookie.

The path is not `/wp-admin`, `/wp-login.php`, `/wp-cron.php`, `/wp-json`, `/xmlrpc.php` or another bypassed endpoint, and the query has none of `rest_route`, `preview`, `customize_changeset_uuid`, `unapproved` or `replytocom`.

The origin answered `200` with `text/html`, set no cookie, did not send `X-WP-Cacheable: 0`, and did not send `Cache-Control: no-store` or `private`.

Stored pages live for 300 seconds. Tracking parameters (`utm_*`, `fbclid`, `gclid` and a few more) are stripped from the cache key and the remaining query is sorted, so equivalent URLs share one entry. The client sees a `cf-cache-status` header of `HIT`, `MISS` or `BYPASS`.

`platform-cloudflare-page-cache.php` is WordPress's half of the arrangement. On every front-end response it sends `X-WP-Cacheable: 1` with `Cache-Control: public, max-age=0, s-maxage=300` for cacheable pages, and `X-WP-Cacheable: 0` for logged-in users, previews, searches, 404s and non-`GET` requests.

### Purging

The purge is global. The plugin posts to `/__cache/purge` on the site's home URL whenever content or configuration changes: post save, delete, trash and untrash, comment posts and edits, theme switch, customizer save, plugin activation and deactivation, and menu updates. The Worker authenticates the call with the shared `CACHE_PURGE_SECRET` and bumps a version number stored in KV. Because the version is part of every cache key, every cached page misses at once, and the old entries expire on their own.

Three things to check when purges do not seem to work:

`CACHE_PURGE_SECRET` must be set in the environment WordPress runs in, and `WP_HOME` must be defined. If either is missing, the plugin silently does nothing.

The Worker needs its `CACHE_KV` binding. Without it the purge endpoint answers `501` and the version stays at `0`.

Each Worker isolate remembers the version for 10 seconds, so allow that long for a purge to be seen everywhere.

### What the public plane refuses

On the NixOS module, setting the plane role to `public` makes Caddy redirect `/wp-admin` (except `admin-ajax.php` and `admin-post.php`) to the admin URL, redirect `/wp-login.php` unless `plane.allowLogin` is set, return `403` for `/xmlrpc.php`, return `404` for `wp-cron.php`, `wp-signup.php`, `wp-activate.php` and `wp-links-opml.php`, and return `404` for any PHP file under `wp-content` or `wp-includes`. The edge Worker applies the same kind of guard before the cache runs.

The design choice worth understanding is that the public plane is not read-only. Checkout, donations, comments and form posts are all writes that visitors are supposed to make. What it enforces instead is a session rule: nobody privileged can hold a session there. Each plane declares a different site URL, so the auth cookie names differ and an admin cookie is not read on the public host, and `platform-public-plane.php` refuses to authenticate staff even with a correct password. With no privileged session possible, WordPress's own capability checks deny every administrative route.

## User enumeration protection

`platform-user-enumeration.php` closes four ways of learning usernames, with no settings and no database writes. It replaces the stop-user-enumeration plugin, which rewrites an option on every page load and so costs a round trip per view on a remote database.

| Leak                                                       | What the platform does                                                                                                             |
| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `?author=<n>` probes, which redirect to `/author/<login>/` | Anonymous requests where `author` contains a digit, or is an array, get a 403. Named values such as `?author=jane` are left alone. |
| The users REST routes under `/wp/v2/users`                 | The routes' permission callbacks require a logged-in user, then run the original check.                                            |
| The users sitemap                                          | The provider is removed, so authors' URLs are not listed.                                                                          |
| oEmbed responses                                           | The `author_url` field is removed.                                                                                                 |

Logged-in users are unaffected, because the block editor's author picker needs the users endpoint. The REST check is applied on each route's permission callback rather than through `rest_pre_dispatch`, because another plugin returning `null` from that filter would quietly undo a short-circuit there. The edge Worker adds its own 401 for the same routes when the request carries no auth cookie or `Authorization` header.

## Audit a dump before you restore it

A MySQL dump from a host you do not control is an input, not a trusted file. It can carry triggers, stored routines, views and `DEFINER` clauses that execute on the new server the moment they are restored. A trigger on `wp_comments` that creates an administrator whenever a comment matches a phrase is a persistence backdoor, and restoring the dump faithfully would migrate the compromise along with the content.

`audit-mysql-dump` is a Python script with no dependencies, packaged as a flake output. Run it before any other migration step:

```
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">nix</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">run</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">github:Avunu/wordpress-nix#audit-mysql-dump</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">--</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">dump.sql</span>
```

It reports:

Every trigger, procedure, function and view, by name, plus a count of `DEFINER` clauses.

Any trigger or routine that inserts into, updates or replaces rows in the users tables, flagged as a privilege escalation.

Every account whose `wp_capabilities` contains `administrator`, with login, email and registration date.

A fingerprint for accounts whose capability was written as the string `"1"` instead of WordPress's own `b:1` form, which means something issued SQL directly.

Abridged output from the repository's test fixture looks like this:

```text
EXECUTABLE OBJECTS FOUND. These run on the new server once restored.
  trigger  after_insert_comment
  routine  housekeeping
  view     wp_a_view
  definer  1 DEFINER clause(s)

!! PRIVILEGE ESCALATION: these write to the users tables, which is
!! what a persistence backdoor does. Treat the source host as compromised.
!!   after_insert_comment
```

The exit code is the gate: it is 1 when any trigger, routine or view is found, and 0 otherwise, so a migration script can stop on it. With `--strip` it exits 0 because it has already written a sanitized copy. The administrator list never changes the exit code, so read it yourself.

### Strip the executable objects

When the dump is otherwise good, write a sanitized copy:

```
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">nix</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">run</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">github:Avunu/wordpress-nix#audit-mysql-dump</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">--</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">dump.sql</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">--strip</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">-o</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">clean.sql</span>
```

`--strip` removes triggers, procedures, functions, views and `DEFINER` clauses, and leaves content and schema as they were. The result audits clean. Other options are `--json` for machine-readable findings, `-` as the filename to read from stdin, and `--allow-executable` to exit 0 even when objects were found, which you should not use in a migration.

The tool does not delete accounts, on purpose. Editing `INSERT` statements risks corrupting content, and rows are easier to remove once they are in a database. The report prints the `DELETE` statements to use after restoring, and three `SELECT COUNT(*)` queries against `information_schema` to confirm nothing executable survived.

Warning

A finding in the escalation section means the source host should be treated as compromised, not just the dump. Removing the trigger does not explain how it got there. Rotate credentials and keys on the source before you trust anything else from it.

### Limits to know about

The administrator check looks for the literal `wp_capabilities` meta key. On a site with a custom table prefix it can report none. If that surprises you, check the prefix.

The audit is not wired into `wp-import` or the other conversion tools. Run it yourself first, then continue with `restore-core-keys`, `mysql-to-sqlite` and `sqlite-to-turso`.

`mysql-to-sqlite` does not migrate triggers, procedures, functions or events, and lists each one it skips. Read that list too. The audit is the earlier and stricter gate.

## Related documents

[WordPress on FrankenPHP with wordpress-nix](/kb/nixos/wordpress-on-frankenphp-with-wordpress-nix/), for deploying and developing the sites these plugins run on.

[Database Optimization Queries](/kb/wordpress/database-optimization-queries/), for measuring and cleaning up meta bloat on a MySQL-backed site.

Sources

- [github.com/Avunu/wordpress-nix](https://github.com/Avunu/wordpress-nix)
- [github.com/Avunu/wordpress-sqlite-anywhere](https://github.com/Avunu/wordpress-sqlite-anywhere)
- [wordpress.org/plugins/index-wp-mysql-for-speed](https://wordpress.org/plugins/index-wp-mysql-for-speed/)

Need help with NixOS?

Our notes can take you a long way, but sometimes you'd rather have someone who's done it before.

[Managed infrastructure](/services/infrastructure/)

[← PreviousWhy Nix for business systems](/kb/nixos/why-nix-for-business-systems/)

CC0This article is in the public domain ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)), code samples included. Use it however helps you.

On this page

- [How the platform plugins are delivered](#how-the-platform-plugins-are-delivered)
- [Performance keys for SQLite engines](#performance-keys-for-sqlite-engines)
- [How and when the keys are added](#how-and-when-the-keys-are-added)
- [The hardening mu-plugins](#the-hardening-mu-plugins)
- [Page cache and the two planes](#page-cache-and-the-two-planes)
- [The edge cache](#the-edge-cache)
- [Purging](#purging)
- [What the public plane refuses](#what-the-public-plane-refuses)
- [User enumeration protection](#user-enumeration-protection)
- [Audit a dump before you restore it](#audit-a-dump-before-you-restore-it)
- [Strip the executable objects](#strip-the-executable-objects)
- [Limits to know about](#limits-to-know-about)
- [Related documents](#related-documents)

[Back to top↑](#top)

Services

- [ERP implementation](/services/erp/)
- [Odoo](/services/erp/odoo/)
- [ERPNext](/services/erp/erpnext/)
- [Custom software](/services/custom-software/)
- [Devices & IoT](/services/devices-iot/)
- [Websites](/services/websites/)
- [Infrastructure](/services/infrastructure/)

Resources

- [Our work](/work/)
- [Open source](/open-source/)
- [Knowledge base](/kb/)
- [Insights](/insights/)

Company

- [About](/about/)
- [Team](/about/team/)
- [Partners](/partners/)
- [Contact](/contact/)

Clients

- [Project portal](https://erp.avunu.net/projects)
- [Invoices](https://erp.avunu.net/)
- [Support](https://erp.avunu.net/)

[![Avunu](/brand/avunu-logo-light.svg)](/)[\<av-icon data-jx-static>\<svg viewBox="0 0 24 24" width="20" height="20" fill="currentColor" stroke="none" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false">\<path d="M20.400 20.500h-3.600v-5.600c0-1.300 0-3-1.800-3s-2.100 1.400-2.100 2.900v5.700H9.400V9h3.400v1.600c.5-.9 1.600-1.900 3.400-1.900 3.600 0 4.300 2.400 4.300 5.500v6.300zM5.300 7.400a2.100 2.100 0 1 1 0-4.100 2.100 2.100 0 0 1 0 4.100zm1.800 13.100H3.600V9h3.500v11.500zM22.200 0H1.800C.8 0 0 .8 0 1.700v20.600c0 .9.800 1.700 1.800 1.700h20.400c1 0 1.800-.8 1.800-1.700V1.700C24 .8 23.200 0 22.200 0z">\</path>\</svg>\</av-icon>](https://www.linkedin.com/company/avunu)[\<av-icon data-jx-static>\<svg viewBox="0 0 24 24" width="20" height="20" fill="currentColor" stroke="none" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false">\<path d="M12 .3a12 12 0 0 0-3.8 23.4c.6.1.8-.3.8-.6v-2c-3.3.7-4-1.6-4-1.6-.6-1.4-1.4-1.8-1.4-1.8-1-.7.1-.7.1-.7 1.2.1 1.8 1.2 1.8 1.2 1 1.8 2.8 1.3 3.5 1 .1-.8.4-1.3.7-1.6-2.7-.3-5.5-1.3-5.5-5.9 0-1.3.5-2.4 1.2-3.2-.1-.3-.5-1.5.1-3.2 0 0 1-.3 3.3 1.2a11.500 11.500 0 0 1 6 0c2.300-1.500 3.300-1.200 3.300-1.200.6 1.700.2 2.900.1 3.200.8.8 1.200 1.900 1.200 3.200 0 4.600-2.800 5.600-5.500 5.900.4.400.8 1.100.8 2.200v3.300c0 .3.2.7.8.6A12 12 0 0 0 12 .3">\</path>\</svg>\</av-icon>](https://github.com/Avunu)[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

Avunu LLC · 948 East Philadelphia Street, York, PA 17403 · (717) 814-8540Knowledge base articles are in the public domain[Privacy](/privacy/)[Terms](/terms/)
