For products that host these assets for their own users: game platforms, world builders, agents that hand somebody a scene. Every other plan here licenses you to use the catalogue, and any product may link to the free models. This one licenses you to host it, HD editions included.
Pick the assets you want live. Serve them to as many users as your tier covers. Everything your users build with them stays theirs permanently, including after our agreement ends.
Questions first? Ask before you subscribe
Questions first? Ask before you subscribe
Questions first? Ask before you subscribe
Tell us how many users you serve and we reply the same day
Every tier covers each asset in both editions, the low poly and the HD (high poly and textured, on 1,975 assets today and more each week), as the GLB and the ES module, with its remix knobs, server-side remix baking, and updates to the assets you hold. Full catalogue is an agreement we write together rather than a checkout, and so is anything past it: more than 100,000 users a month, or terms of your own. Start the conversation.
Take the 3605 published assets one at a time and build the exact set your product needs: forty vehicles, or every animal, or the props your users keep asking for. One asset, one slot.
A kit is a designed range, not a folder: one palette, one grid module, one style contract, so the parts look like a single world. The 54 kits built so far run from 26 to 122 parts, about 61 typically. Each part takes one slot, so a 400-slot tier is roughly 6 kits.
Mix them however you like, and swap what is not working: your monthly swaps free a slot and fill it with something else, with 30 days to take the released asset off your platform. New assets land at roughly 145 a week and can fill a free slot or a swap at any time.
You tell us what you want live: this kit, that kit, and forty props by name. Those assets take your slots, and the assigned list is the licence, the record of what you may serve. Nothing is metered afterwards: no request billing, no download counting, no attestation, no auditor, no phone-home in the files. A swap changes the list, and the user band on each tier is a size we agree at the start and revisit at renewal rather than a number anyone has to prove.
No. Any product, including one where other people build with them, can load the free low poly models straight from polyfork.dev as each user picks one, under the standard licence and with no fee. This licence is for keeping your own copies: on your servers or CDN, in your own asset library, or as downloads from you, so your platform does not depend on ours. The free mesh files are also CC BY 4.0, so you may host those yourself with a credit line; this licence covers the ES modules, which carry the sliders, hosting without a credit, and the HD editions, which it is the only way to serve to your users. The line is drawn on polyfork.dev/licensing.
One asset you are licensed to serve, in both editions: the low poly and, where the asset has one, the HD, high poly and textured. Slots are taken by assignment rather than by usage: name a kit and each of its parts takes a slot, or pick assets one by one. The assigned list is the record of what you hold, so there is nothing to report, no usage audit, and no metering code anywhere in your product.
Yes, and most platforms should. A kit is a designed range that shares a palette, a grid module and a style contract, so 61 parts taken together look like one world rather than like 61 purchases. Kits here run from 26 to 122 parts, and each part it contains takes one slot. Mix the two freely: two kits and forty cherry-picked props is a perfectly normal shape.
It removes the slot list. Every asset, every kit and everything published while you are subscribed, with nothing to assign and nothing to swap. It exists because a slot ceiling has a shelf life: this catalogue grew by 1083 assets in the last 30 days, so a fixed count that means "everything" today stops meaning it within weeks. With no slot list, the user band and the terms are the whole agreement, which is why this tier is priced on a call rather than sold at a checkout: from $2,900 a month, sized to your platform.
Improvements to assets you hold are included: new knobs, new formats, remix baking, fixes. New catalogue assets, including commissioned characters, skins and steered kits once they publish, fill a free slot or a swap like anything else. Commissioning itself is separate: steering a kit or ordering a custom character or skin is priced per order, for licensees the same as for anyone, and offering Polyfork generation to your own users as a feature of your product is its own agreement rather than part of this one.
Anything they build on your platform with a licensed asset carries the standard Polyfork licence: commercial use, any number of projects, no attribution, no expiry. That licence is theirs directly and it survives the end of this agreement, so a game shipped on your platform never becomes unlicensed because our contract lapsed.
Yes. Cache them, put them on your own CDN, bundle them into your build. We meter on delivery rather than on requests, so serving them from your own edge costs you nothing extra and needs no permission. Mirroring assets that are not in your slots is the line.
No, and this is the one clause with no version of it we will sell. The assets, their source, renders, briefs and metadata are not training, fine-tuning, evaluation or benchmark data, and not raw material for a generator that produces 3D output. Generating variants by calling an asset's published knobs is a different thing entirely and is exactly what they are for.
The Founders Club is permanent access for your own team's work, which is the right way to prototype and to decide what to slot. It is a per-seat licence, so it does not cover hosting the assets for other people, the same way it works at every asset library. Your founding payment comes off your first platform invoice.
You stop serving the assets within 30 days, and everything your users already built stays licensed to them permanently. Terms are monthly or annual, cancellable at the period end, with 30 days to fix anything either side gets wrong.
How many assets you want live, and roughly how many users you serve. We will confirm the tier and start on the integration in the same week.
Email [email protected]