Where Sketch cost vs self-hosted Penpot actually differs
Self-hosted Penpot removes the per-editor license line from a Sketch renewal, but it adds infrastructure, operations, migration and support costs that a vendor subscription currently covers. A design leader holding a Sketch renewal or Private Cloud quote should compare the full set of components, not the license alone. Pull current Sketch prices directly from Sketch, including per-editor plan rates and any Private Cloud fee, and ask for them in writing with the seat count and term. For reference, Penpot's pricing page, read in October 2026, lists Professional at $0, Unlimited at $7 per editor per month capped at $175 per month, Enterprise at $25 per member per month, and a Private Server at $50k per year. The Private Server figure is Penpot's hosted offer, so it is a comparison point, not the price of running Penpot on your own servers.
The self-hosted costs fall into recurring and one-time groups. Recurring costs include the compute for the Penpot application, a PostgreSQL database (version 13 or later, the only database Penpot supports), a Valkey instance for websocket notifications, and file storage on the filesystem or an S3-compatible service such as MinIO. Your platform team also carries backups, TLS, monitoring and version upgrades, and those are staff hours, not line items on a vendor invoice. One-time costs include the initial deployment, which Penpot documents through Docker Compose or its official Helm chart, and the migration of existing Sketch files. Storage and staff effort grow with file volume and the number of environments, so ask any implementation partner for a fixed-scope quote that separates setup from ongoing support.
The break-even point depends on headcount. As arithmetic from the published figures, the Unlimited cap of $175 per month is reached at 25 editors, so a team of that size pays the same monthly amount for Penpot Cloud Unlimited no matter how many more editors it adds. Before deciding, price three things: the annual Sketch cost at your exact seat count, the one-time migration of your current libraries and files, and the identity work to connect Penpot to your directory through OpenID Connect or LDAP. Confirm the migration path with Penpot's own documentation, since Sketch files do not convert directly, and plan for staff time to rebuild the most complex components.
Cost components on each side, one-time versus recurring
This table compares what each option costs by component, from licenses and hardware to servers, PostgreSQL, object storage, backups, setup and upgrades. Read the timing column to separate one-time setup from recurring charges. The main takeaway is that self-hosted Penpot removes the license line, but it moves operations, backups and file rebuilds onto your team or a provider you choose.
| Cost component | Sketch (per-editor, Mac-only or Private Cloud) | Self-hosted Penpot | One-time or recurring |
|---|---|---|---|
| Software license or subscription | Per-editor plans, or Mac-only licenses without collaboration. Confirm current terms with Sketch. | No license fee. Penpot is licensed under MPL-2.0. | Sketch: usually recurring for plans. Penpot: none |
| Mac hardware and OS for designers | Designers need macOS for the Sketch app. | Browser-based workspace; designers can use the machines they already have. | One-time per device, refreshed on your schedule |
| Server compute | None for desktop use. Confirm what Private Cloud hosting includes and who runs it. | Virtual machines or containers you provision, sized to team load, deployed with Docker Compose or Helm. | Recurring, for as long as the server runs |
| PostgreSQL | Not applicable | PostgreSQL 13 or later is required. The software is free, but administration and patching take staff time. | Recurring, through administration and patching |
| Object storage (filesystem or S3-compatible such as MinIO) | Confirm storage limits and any overage terms in your plan. | Filesystem or an S3-compatible store such as MinIO. Capacity grows with uploaded assets. | Recurring, as storage grows |
| Valkey and backups | Not applicable. Sketch operates its own service. | Valkey coordinates websocket notifications. Backups of PostgreSQL and object storage need storage and restore tests. | Recurring, for backup storage and restore testing |
| Implementation, configuration and SSO | Admin setup for workspace and SSO, if your plan includes it. | Setup of email login, Google, GitHub, GitLab, OpenID Connect or LDAP, plus environment configuration. | One-time setup, with periodic changes |
| File migration and rebuilds | Existing Sketch files stay in Sketch while the license runs. | No Sketch importer is documented, so plan to rebuild artboards, symbols and libraries in Penpot. | One-time per migration project |
| Upgrades, release testing and support | Vendor manages cloud upgrades. Confirm how Mac app updates are handled. | Your team tests and applies releases. Partner support can be contracted as a retainer or fixed scope. | Recurring for testing and support; partner fees depend on scope |
How per-editor pricing scales against a fixed server bill
The core question is how each cost line grows over time. Per-editor pricing grows with headcount and tenure, because every new designer, contractor or returning seat adds a charge that recurs each billing period, and a renewal can change the rate. Self-hosted Penpot grows along a different axis. Its cost follows load (concurrent editors, file size, asset volume) and availability needs (redundancy, backups, maintenance windows), and most of it stays flat for a given design. The two curves cross, so the decision depends on where your team sits today and how it will change over the period you plan to keep the tool.
Treat the Penpot cloud prices as a reference point only. Penpot's pricing page, as read in October 2026, lists Unlimited at $7 per editor per month with a $175 monthly cap, Enterprise at $25 per member per month, and a Private Server at $50k per year. These are vendor offers for hosted or managed service. The Enterprise and Private Server figures describe what the vendor charges for those offers, and they say nothing about what your own servers, database and staff will cost. Penpot is licensed under the Mozilla Public License 2.0, so the software itself carries no license fee, but running it still requires infrastructure and people. Confirm current tiers directly before you model anything.
To find the break-even point, collect written quotes from Sketch for the editor count and tier you need. Ask whether Private Cloud pricing is charged per editor or per organization, and get the renewal, true-up and seat-reduction terms in writing. Annualize each per-editor line, then divide your expected yearly self-hosted cost by the per-editor annual price to find the editor count at which self-hosting costs less. The self-hosted side should list the fixed components: server capacity, PostgreSQL, Valkey, object storage for uploads, backups, monitoring, applying Penpot releases, and the staff hours or support retainer that keeps them running. Mark each item as one-time setup or recurring. Illustrative only: if the yearly self-hosted cost were 60,000 and the per-editor quote worked out to 1,200 a year, the break-even would fall at 50 editors.
What moves the cost comparison most
Sketch is priced per editor and Penpot self-hosted has no license fee, so the comparison turns on how many people work in the tool and what the organization must run around it. The six factors below change the total in different directions, and each one is worth pricing with a real headcount and file inventory before comparing quotes.
Editors and viewers
Per-editor plans scale with the number of people who edit files, while viewers and stakeholders who only review designs may or may not count against your seats, depending on the plan. Self-hosted Penpot has no per-seat license fee, so the cost of additional users is mostly identity, storage and support effort. Ask Sketch for the exact seat rules for viewers and guests before you count headcount.
File and asset volume
Penpot stores uploaded objects on the filesystem or in S3-compatible storage such as MinIO, so large libraries of images, fonts and exported assets add storage capacity, backup size and restore time on your side. The growth rate of design files is the main driver here. Measure current library size and project growth before sizing disks or buckets.
Availability and recovery targets
A cloud subscription shifts uptime and backup responsibility to the vendor, while a self-hosted instance makes you responsible for redundancy, database backups and tested restores of PostgreSQL and object storage. The stricter the recovery targets your design teams need, the more infrastructure and operator time you add. Confirm the targets with your business owners before pricing the setup.
SSO and identity integration
Self-hosted Penpot supports email and password login by default, plus Google, GitHub and GitLab OAuth, generic OpenID Connect and LDAP. Connecting it to your corporate identity provider and group model takes configuration and testing, and the effort rises with the number of applications and custom attribute mappings. Check which login method your identity team will support before estimating this work.
Sketch Mac licenses still needed
Teams that rely on Sketch plugins, Mac-only workflows or legacy files may keep some Mac licenses running during a transition, which means paying for two tools for a period. The number of retained licenses depends on how many designers depend on plugins that have no Penpot equivalent. Inventory plugin use per designer, then decide how long parallel licenses are needed.
In-house operations skills
Running Penpot means operating Docker Compose or the official Helm chart, PostgreSQL 13 or later, and Valkey for websocket notifications. If these skills exist in your platform team, the cost is mostly time; if not, you will pay for training, an external partner or a retainer. Confirm who will patch, upgrade and monitor the stack before choosing a deployment target.
How to build the comparison with your own numbers
This sequence turns your current Sketch spend and Penpot's published pricing into a three to five year comparison in one currency, built from inputs your finance and infrastructure teams have confirmed. Each step produces a figure you can defend in a renewal or budget review.
Export current Sketch invoices and seat counts
Finance or the license owner pulls the last several Sketch invoices and the admin console seat report, so every paid editor, plan tier and add-on is accounted for. Confirm the billing currency, any tax treatment, and whether the Private Cloud tier is billed separately from per-editor plans. You are done when you have a single table of monthly and annual charges that ties back to the invoices.
List editors, viewers and Mac-only users
Design leads and IT sort every person who touches Sketch into groups: full editors, reviewers who only view or comment, and people who run Sketch on a single Mac without collaboration. Record which groups are paid today and which are covered by a shared or free arrangement. The output is a headcount per group that you will use for both the current cost and the Penpot scenario, since Penpot's pricing counts members differently by plan.
Read Penpot's current pricing directly
Open Penpot's pricing page on the day you build the model, because plan names, per-member rates and caps change. Copy each plan's price, billing unit and any cap into your sheet, along with the date you read it. Confirm with Penpot sales or the vendor documentation whether the plan you need covers your member counts, support level and any private server option. The check is a dated pricing table that matches the headcount groups from the previous step.
Price the Docker Compose or Helm deployment
Your infrastructure team costs the servers that would run Penpot, using the Docker Compose or Helm options documented in Penpot's technical guide, in your own cloud account or data center. Include compute for the application, the websocket coordination service, a load balancer, backups and any non-production environment for testing upgrades. Ask your cloud or hardware vendor for quotes, and mark which lines are one-time (hardware, initial setup) and which recur (compute, bandwidth, backup retention). The output is a monthly infrastructure line with its assumptions written down.
Estimate storage from existing file sizes
Measure the size of your largest Sketch files and the number of libraries, then multiply by expected growth and your retention rules for version history and backups. Penpot stores uploaded objects on the local filesystem or in an S3-compatible store such as MinIO, so the storage choice affects both the price and the operating effort. Ask your storage team to quote the chosen option and the backup copies it needs. The check is a storage projection for year one, year three and year five.
Add PostgreSQL and Valkey operations
Penpot requires PostgreSQL, with version 13 or later recommended, and uses Valkey for websocket notification coordination. Your database and platform teams should estimate the hours needed to provision, patch, monitor, back up and test restores for both services, and whether these run on existing shared platforms or new dedicated instances. Record any managed database fees separately from the internal staff time. You are done when every database and cache component has an owner and a monthly operating estimate.
Model migration and file rebuild effort
Sketch files cannot be assumed to convert cleanly, so design leads should review a representative sample of each file set and record how long rebuilding components, libraries and prototypes would take, grouped by project. Penpot's documentation for Sketch-specific import should be checked directly with Penpot before you rely on it, and you should confirm whether any Figma-to-Penpot exporter in use covers your files. Your output is a one-time migration estimate per file set, expressed in person-days and cost, with the assumptions noted.
Compare three to five years in one currency
Build a comparison sheet with the current Sketch cost and the Penpot scenario side by side, placing one-time costs (migration, setup, hardware) in the first year and recurring costs (plans or infrastructure, database operations, storage, support, upgrades) in every year. Convert all amounts to a single currency using a rate and date your finance team confirms, and add support and upgrade time explicitly, since self-hosting shifts those tasks to your staff or a service partner. Ask your finance team to review the model for discount rates and the renewal terms of the Sketch contract. The finished model should show cumulative cost by year for each scenario, with every input traceable to a confirmed source.
What the migration work involves and who pays for it
The migration runs in stages, and the largest one-time cost is the rebuild, not the software. Start with an inventory of Sketch files, shared libraries, symbols, text styles and colour assets, and record which files are live product work and which are archives. Count the components that other files depend on, because that number, rather than the seat price, drives the effort. No Sketch importer is documented for Penpot, so each library component and token set has to be recreated in Penpot's workspace or through the API and plugin system. Ask any services partner to price the work per library and per file tier, not as a flat project fee, and to state who owns the rebuilt component names and token structure at handover.
Validation is where teams find the gaps. Check each rebuilt component against its Sketch original at the sizes and states used in production, and confirm that design tokens resolve correctly in Penpot's native token model. Export a sample of frames as SVG and CSS and compare the output with what developers receive today, since open standards such as SVG and CSS are a core reason to choose Penpot. Confirm with the Penpot project which exporter behaviours and plugin dependencies your teams rely on before retiring anything. The Penpot technical guide covers the server settings you will need during this phase, including the single sign-on and storage choices that onboarding depends on.
Onboarding and seat retirement come last, and both carry recurring costs that are easy to miss. Plan user training, login setup and a cutover date for each team, and keep Sketch licences active until the last dependent file is verified, because Sketch's per-editor plans and Mac-only licences bill for each seat until they are removed. Your own staff time covers design review, governance and library upkeep after go-live, while server operation, backups and upgrades continue indefinitely. The Figma exporter plugin is a separate path that handles Figma files only, so it does not help with Sketch content and should not be counted as a Sketch migration tool in your estimate.
Questions buyers ask before comparing costs
How much does it cost to self-host Penpot?
The Penpot software has no license fee, so the cost is the infrastructure and people that run it. Those components are the application server, PostgreSQL (version 13 or later), Valkey for websocket notifications, object storage on the filesystem or an S3-compatible store such as MinIO, backups, and the staff time to deploy, patch and monitor the stack. For reference only, Penpot's cloud pricing page, as read in October 2026, lists Unlimited at $7 per editor per month capped at $175 per month, and a Private Server at $50k per year. Ask any provider to show its own per-component estimate for your user count, storage growth and redundancy needs, so you can compare it with the Sketch quote line by line.
Is Penpot free to use?
Yes, the software itself carries no license fee. Penpot is licensed under the Mozilla Public License 2.0 and is an open-source project of Kaleidos, so your organization can install, run and modify it without paying for the code. Confirm with your legal team how MPL 2.0 obligations apply to any changes you distribute, and note that the license does not cover the hosting, staffing or support you choose to buy.
How long does a migration from Sketch take?
The duration depends on the number of files, how many use components and libraries, how much prototyping logic the designs contain, and how much of the stack your team already runs. Sketch files do not have a documented importer for Penpot, so budget time for rebuilding or reconstructing key assets. Also plan for a parallel period while designers check results. Ask any partner to give a fixed-scope timeline based on an inventory of your actual files, rather than relying on a generic figure.
Can our team run Penpot without outside help?
A team with container and database experience can run Penpot, but the skills must be present, not assumed. You need people comfortable with Docker Compose or the official Helm chart, PostgreSQL administration, Valkey, and either filesystem or S3-compatible storage. Someone must also own SSO configuration (OpenID Connect or LDAP), TLS, backups, restore tests and version upgrades. If those skills are thin, a fixed-scope implementation with documentation and handover is one option, and an ongoing support retainer is another.
What recurring costs remain after we self-host?
Recurring costs fall into four groups: compute and network capacity for the application, PostgreSQL and Valkey; storage and backup retention, which grows with design files and version history; staff time for patching, monitoring and upgrades; and any paid support or retainer you buy. Costs for the first three are mostly fixed by your infrastructure choices, while the fourth depends on your support model. Ask for a month-by-month cost model that separates these groups so you can see what changes as the team grows.
How should we compare this with a Sketch Private Cloud quote?
Compare the two on the same basis: who operates the servers, who applies updates, what login options exist, where data is stored, and what each option costs per year. Sketch Private Cloud is a vendor-operated tier, so its cost includes the vendor's operations, while self-hosted Penpot moves those duties to your team or your implementation partner. Ask Sketch to state its update cadence, data location and SSO support in writing, then price your own infrastructure and staff time against those answers.
What should we ask a partner to include in a quote?
Ask for a written scope listing the deliverables: environment design, Penpot deployment (Docker Compose or Helm), PostgreSQL and Valkey setup, storage choice, SSO integration, backup and restore testing, file migration approach, user training and documentation. Also ask what is excluded, how acceptance is tested, who handles upgrades after go-live, and whether support is a separate retainer. DeployOpen plans and implements self-hosted platforms in your own infrastructure and provides fixed-scope engagements, with pricing following from that written scope.
When self-hosting the cost comparison points the other way
For a small design team, a hosted plan is often the cheaper option, and the self-hosted route only makes financial sense once its fixed costs are spread across enough people. Penpot's cloud pricing, as read in October 2026, lists a Professional tier at $0, so a few editors who do not need a private environment may pay nothing for the hosted service. Sketch's per-editor plans and Mac-only licenses also carry a small, predictable cost for a handful of designers. Before deciding, count the editors who will actually edit files, not the people who only view them, and compare that number against the hours your team would spend running a server, PostgreSQL, storage and upgrades.
The comparison also favors the hosted option when nobody on your staff can run the stack. Self-hosted Penpot is deployed with Docker Compose or the official Helm chart, and it depends on PostgreSQL 13 or later, Valkey for websocket notifications and either filesystem or S3-compatible storage. Ask who will patch these components, restore backups and answer an incident at 2 a.m. If that work would fall to a designer or a generalist administrator with no time for it, the hidden labor cost can outweigh the license savings. Also weigh your residency position honestly. If no regulator, contract or internal policy requires design files to stay on your own servers, a hosted workspace may meet your needs at lower total cost.
Finally, Sketch remains the better fit for some teams, and that is a legitimate reason to stay. If your workflow depends on Sketch plugins, Mac-specific shortcuts or a library of symbols your designers have built over years, the cost of rebuilding that workflow in Penpot belongs in your estimate. Confirm which plugins you use and whether equivalent Penpot plugins or API-based scripts exist for each one. Penpot's Figma exporter does not support prototyping settings, and no Sketch importer is documented, so expect manual rebuild work whichever direction you move. Price that rebuild time as a one-time cost alongside the recurring license and hosting figures, then compare the totals over the period you plan to use the tool.
How DeployOpen scopes a fixed-price Penpot implementation
DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted Penpot inside your own infrastructure, from cloud accounts to data centers or air-gapped networks. Most engagements are fixed-scope, so the cost components discussed on this page are written down before work starts.
How we scope
- Inventory the Sketch seats, Mac-only licenses and file libraries that the Penpot migration must cover
- Agree the hosting target, PostgreSQL version and object storage choice in the written scope
- Define which login methods, such as OIDC single sign-on or LDAP, are in and out of scope
- Confirm the Penpot release to deploy and how upgrades will be handled after handover
How we build
- Deploy Penpot with Docker Compose or the official Helm chart in your environment
- Configure PostgreSQL, Valkey for notifications, and filesystem or S3-compatible storage such as MinIO
- Plan the rebuild effort for Sketch files, since no Sketch importer is documented, and test sample files
- Test imports, team permissions, and realtime collaboration before users are onboarded
How we hand over
- Document the deployment, configuration keys, backup routines and restore steps for your team
- Provide runbooks for user onboarding, offboarding and file ownership in your environment
- Deliver the implementation records and control evidence your compliance assessors may request
- Walk your administrators through upgrade and rollback procedures before the engagement closes
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer after handover
- Apply Penpot patch releases in a staging copy before production, as agreed in the scope
- Re-test authentication, storage and backups after each upgrade or infrastructure change
- Ask your team to confirm response expectations and maintenance windows in the retainer terms
