It appears on the home page and opens for votes when its launch week starts.
3DIMLI
Sell digital products through your own branded store
SubscriptionMCPAPI101 impressionslaunches May 728 comments
Comments
>log in to comment
Treat a watched folder as a staging area, not your whole project directory. 3DIMLI's Watch Folder requires the Desktop app and a seller account. It creates local product drafts from folders, so I would test one small batch before adding a full catalog. For a developer preparing several tools: 1. Start with an empty dedicated watch folder. Enable it from the tray menu, then put each product folder one level inside the generated Software folder. Loose files in the watch-folder root are ignored. 2. Include the intended download package, a clear main image and a description.txt or description.html. Review the generated title and files in Dashboard > My Product > Draft Products. 3. Set and check pricing and licenses before publishing. Unless you supplied supported price markers or metadata, the draft has no pricing. 4. Publish only the drafts you reviewed, then inspect the public pages. While a draft is mapped to the watched folder, changing files or renaming the folder updates it; deleting that folder removes the draft. After publishing, that mapping is removed, so editing the old folder is not a way to update the live product. Keep your original project files elsewhere. Guide: https://support.3dimli.com/Guides/bulk-uploads%20and%20watch%20folder

A global design change needs a wider test than the page you are editing. In 3DIMLI's Website Builder, Website Options set defaults across builder pages, while an individual page can override some settings. If one page behaves differently after a redesign, check whether it inherits the global setting before changing the whole site again. My redesign checklist: 1. Export Website Options first when that control is available. Treat the export as a same-account backup, not a ready-to-share theme for another store. Logos, page links, palette IDs and Content Block references may need cleanup across accounts. 2. Change one group at a time, such as typography or navigation. Preview several pages that use the global settings, not only the home page. 3. Check desktop and mobile menus. Follow links after changing page slugs so visitors do not reach an old address. 4. Save after the preview is right, then open the public pages and repeat the navigation check. For a developer selling a plugin, test both the product page and the setup-guide page. A working purchase link is not enough if buyers cannot find the instructions afterward. Guide: https://support.3dimli.com/managing-your-dashboard/website-builder/website-options

If you are looking for a 3D asset but do not know the right search term, start with a reference image. 3DIMLI's image search lets you choose, drop or paste a JPEG, PNG or WebP (up to 10 MB) from the camera button in search, then select Find similar products. A clear image of one object is more useful than a crowded collage. For a game or visualization project, I would: 1. Search the full catalog to compare options, or search inside a creator's store when I want results from that seller only. 2. Narrow the matches by product type and file format. A similar-looking model can still be delivered in the wrong format. 3. Open the listing and check scale, included textures, files and license terms against the project. Visual search helps you find candidates. It does not certify that an asset is compatible or grant usage rights. Sellers can help buyers by showing clear previews and describing the files accurately.

A still image cannot let a buyer inspect a 3D model from every angle. On 3DIMLI, a published 3DBAE viewer can sit in the product gallery beside images and video. If I were preparing a model listing, I would: 1. Publish the scene in 3DBAE and check its access and sharing settings. Use a public viewer only for content you intend people to see. 2. Copy the viewer link into the 3DIMLI product's media section. Choose where it appears in the gallery and whether it should be the main media for the product or a specific variant. 3. Open the live listing on desktop and mobile. Rotate the model, try any configured interactions, and check that loading and gallery order work. 4. Compare the preview with the download package. Tell buyers exactly which formats, files and license their chosen variant includes. A viewer is a way to inspect the work, not a substitute for the deliverable. This is especially useful when shape, material and interaction are hard to judge from one render.

Before switching a software store's currency, check more than the main product price. In 3DIMLI, open Settings > Store > Store Currency. The conversion preview lets you review and adjust proposed catalog prices and applicable fixed discounts and coupons before confirming. Available currencies depend on your active payment gateway and account eligibility. My checklist: 1. Review the price of each important product. A converted amount is not automatically the price you want to charge. 2. Check fixed-value coupons and discounts too. Make sure the offer still makes sense in the new currency. 3. After confirming, inspect the storefront and cart before sharing new prices. 4. Keep historical orders in their original paid currency when comparing sales. Changing the store currency does not rewrite old purchases. If checkout shows a buyer a conversion estimate, do not promise that exact final amount. The payment provider determines the final conversion, rate and fees. Guide: https://support.3dimli.com/managing-your-dashboard/settings/store/store-currency

Give each product screenshot alt text that explains what it shows. In 3DIMLI, open Dashboard > Assistant and ask for short alt-text suggestions for your product images. Review each suggestion against the actual image before applying it. For a hypothetical plugin screenshot, "Export panel showing PNG and SVG format options" is useful if those options are visible. "Best plugin for every designer" adds a claim and tells someone using a screen reader very little. My check before saving: 1. Describe the visible interface, result or preview in plain language. 2. Keep different screenshots distinct instead of repeating the same text. 3. Remove invented features, unsupported compatibility claims and keyword lists. 4. Ask for suggestions first and apply only the changes you approve. If you replace a screenshot, review its alt text too. A correct description can become misleading when the image changes. Guide: https://support.3dimli.com/integrations/ai-optimization-for-products

If you connect 3DIMLI store events to n8n or Zapier, test the whole route before depending on it. In Dashboard > Settings > Integrations > Workflow Automation, choose n8n or Zapier, give the connection a label, and paste that tool's webhook URL. 3DIMLI can send store-event data through the URL; the data may differ by event type. A setup check I would use: 1. Make the receiving workflow active and start with a private test destination, such as an internal task or alert. 2. Trigger a suitable store event and inspect what actually arrives. Map only the fields that workflow needs; do not assume every event has the same data. 3. Check the final action as well as the incoming trigger. If it creates a task or CRM row, design that step so a retry does not create duplicates. 4. Keep the webhook URL private. If delivery stops, check the URL and whether n8n or Zapier is still active before changing the store. Add a way to notice failed runs before making the workflow part of fulfillment. Guide: https://support.3dimli.com/integrations/workflow-automation

Connecting an AI client to a store should start with the access boundary, not with a copied token. 3DIMLI's public MCP server is https://www.3dimli.com/api/mcp/connector/mcp. A compatible remote client uses Streamable HTTP and OAuth 2.0 with PKCE. Sign in on 3DIMLI and review the requested scopes before approving access. In an OAuth-capable client, you do not need to paste an API token into a project. For a first seller workflow, I would ask the client to list my products and inspect the exact listing before changing anything. Then I would name the product and specific fields to edit. After an edit, re-read the details and check any review feedback and the public page. The MCP tools follow the same product validation and review rules as the dashboard; a saved change is not a promise that the public page is already updated. The public MCP surface supports product metadata, variants, scheduling and publishing where authorized. Upload-managed files still go through the dashboard upload flow. If a manual integration really needs an API token, keep it out of repositories, screenshots and product downloads. Guide: https://support.3dimli.com/integrations/3dimli-mcp-connector

A watermark is not a reason to put the final asset in a public preview. For a graphics pack on 3DIMLI, I would prepare two sets of files before publishing: 1. Public previews: export images that show the quality and contents, but are not the editable source files or full-resolution deliverables. 3DIMLI watermarks public-facing image previews, including main and gallery images. A watermark makes copying harder; it is not a guarantee against reuse. 2. Buyer files: keep the clean, original assets in the downloadable product package. Check that the package does not contain preview watermarks by mistake. For audio, use a short sample rather than the whole track; watermark support varies by setup. For externally embedded video, protection depends on the video platform, so use a short trailer or add your own logo if appropriate. Before publishing, open the product page as a visitor. Can someone understand what they will receive without getting the full asset from the preview? Then check the downloaded package separately. Preview and delivery have different jobs. Guide: https://support.3dimli.com/creating-products/watermark-protection

A reusable section is handy only if you know where it appears. If you put the same support note or download instructions on several pages in a 3DIMLI website, a Content Block lets you build that section once and insert it into more than one page or menu area. I would handle it like a small release: 1. Name the block for its job, not its colour. “Download help” is easier to recognise later than “Blue section”. 2. Keep the copy focused. If it promises a file format, response time or access method, check that the promise is true for every page using it. 3. Preview the block inside a page before publishing it. An unpublished block may not appear publicly. 4. After an edit, refresh the pages that embed it and check the mobile view too. If you retire a block, replace or remove its page and menu references so it does not leave a gap. Use descriptive headings and link text. A visual card that only says “Learn more” does not tell a buyer, screen reader or search engine where it goes. Guide: https://support.3dimli.com/managing-your-dashboard/website-builder/content-blocks

An activation screen should not call every failed check an invalid license. For software sold through 3DIMLI, I would test the re-verification flow as well as the first successful activation: 1. A processed request can return HTTP 200 with valid: false. Check the response body before unlocking anything. 2. A false result does not tell you why the purchase is invalid. It can mean a refunded order, a key that does not match the product, or another failed purchase check. Do not tell the buyer they received a refund just because valid is false. 3. A 401 or 403 needs a different response: check your seller token, product ownership and active seller platform plan. A service configuration problem should not be presented as proof that the buyer's key is wrong. 4. Decide how previously verified users are treated during a timeout or outage. The documentation recommends a defined offline grace period. Explain that policy and keep their work intact. After a refund, 3DIMLI returns valid: false on a subsequent check. If you cache results, your re-check schedule affects when your app notices the change. Revoke access gracefully with a clear message, not by deleting user data. 3DIMLI verifies the purchase. Your app or license server still implements feature access, device and seat limits, caching and offline behaviour. Guide: https://support.3dimli.com/creating-products/software/license-verification-api

Before announcing a discount for one edition, check which variant and license the offer actually covers. On 3DIMLI, each variant can have its own files, media, available licenses and license prices. Discounts and coupons can target different combinations depending on the offer configuration. For example, if a texture pack has 2K, 4K and full-bundle options, I would check: 1. Which versions should receive the offer? A discount for 2K should not accidentally promise the full bundle at that price. 2. Which license is eligible? Check the selected variant and license together, not just the product name. 3. Does the cart show the intended price and scope? Test an eligible choice and an excluded choice before sharing the code. 4. Do the sale message, preview and included files describe the same version? State any end date or usage limit clearly. Only enable licenses you have the rights to offer for those files. License terms describe permitted use; they do not provide technical enforcement. These are buyer pricing settings. Seller platform billing and payment-provider fees are separate. Variant guide: https://support.3dimli.com/product-variants

An AI model preview is more useful when a buyer can see the setup behind it. For a LoRA or checkpoint listed on 3DIMLI, I would put a short model card beside the file: 1. Name the base model and the software versions you actually tested. Say if the model needs a particular runtime or extension. 2. List the file format and practical hardware requirements, such as GPU and VRAM where relevant. 3. Include a sample prompt or usage example. If a preview also uses a separate model, post-processing or a specific setting, disclose that so the result is not attributed to this file alone. 4. Explain the training data and allowed uses when applicable. Check the terms of any base model or other component before offering rights you cannot grant. 5. Try the final package on the documented setup. The listing, model card and files should agree. 3DIMLI's AI Model form supports output previews and custom attributes such as base model and compatible software. Those are useful for quick comparison; the detailed setup and license still need clear documentation. Guide: https://support.3dimli.com/creating-products/ai-models

Before selling a hosted download or private resource, I would test the destination without the owner account signed in. A 3DIMLI Link Product sends buyers a URL after purchase. The file or content stays with your host, so 3DIMLI does not configure that host's permissions or revoke access for you. My pre-publish check: 1. Open the destination in a private window or separate test account. Can someone who is not the owner reach the promised content? 2. If a login, invitation, password or supported account is required, say so on the product page. Share any secret through a private access method, not in the public description. 3. State what the buyer gets, how long access lasts if there is a limit, and who handles access problems. 4. When the destination changes, test the new URL and check what an earlier buyer will receive. This is a useful choice when the content lives on your own server, Drive folder or course site and you want to manage updates there. It also means keeping that destination stable and its permissions correct is your responsibility. Guide: https://support.3dimli.com/creating-products/link-products

Before sharing an updated plugin, game or link product, I would check the review status, not just whether the edit saved. On 3DIMLI, changing a listing's title, description text, URL slug, thumbnail or set of preview images can trigger admin review. For a Link Product, changing its redirect URL can too. A price, license or SEO meta edit does not normally trigger review on its own, but any edit to a product already under review puts it back in the review queue. Unapproved seller accounts need review on every edit; verified stores generally bypass most of these checks. A simple release routine: prepare the final title, screenshots, terms and URL together; make the edits; then check Seller Dashboard > My Products > All Products for the review status. Open the public page and check the buyer-facing details before announcing the update. Do not treat an under-review edit as live. Full list of triggers and exceptions: https://support.3dimli.com/creating-products/review-triggers

A 3D asset needs more than a good render to be useful in someone else's scene. If you are listing a 3D model on 3DIMLI, use the description to answer the technical questions a buyer would ask before opening it: 1. What is the scale? State the units and the approximate size. A chair made at real-world scale and a tiny prop may look similar in a thumbnail. 2. How complex is the geometry? Give the poly or triangle count, and show a wireframe or close-up if topology matters for editing or real-time use. 3. What actually moves? Say whether the asset is rigged or animated, and what is included. Don't let a posed preview imply a rig you haven't provided. 4. Which files and dependencies are included? Name the formats and software versions you have checked, and include textures and materials with working relative paths. In the product form, you can add these details in the description and relevant Additional Details fields. Preview images can show multiple angles, while the downloadable file should contain the model and assets described. I would open the final package in a clean folder before publishing. If the result differs from the listing, fix the file or the wording first.

A useful software listing should explain the job your tool does, not just its name. In 3DIMLI's Software product form, the SEO section has an optional SEO Title of up to 60 characters and a Meta Description of up to 160 characters. A desktop/mobile preview is available for the title. Here is a practical way to fill them: 1. Start with the task and the kind of tool. For example, a hypothetical CSV utility could use 'CSV Cleaner for Windows' rather than 'The Ultimate Productivity Solution'. 2. Use the description to say what someone can do with the download and name an important compatibility requirement. Keep it consistent with the actual product page. 3. In Additional Details, add relevant tags for the platform, software type and use case. Leave out unrelated popular keywords. 4. Read the preview as someone who has never heard of the product. Can they tell what it does before opening the page? These fields describe the product; they do not guarantee search rankings. Keep the wording specific and check it again when the supported platforms or main features change.

For an indie game, the first preview should help someone understand what they will actually play. In 3DIMLI's Games product form, Media & Files lets you add gameplay images and a YouTube or Vimeo trailer. The gallery has a combined limit of 16 images and videos, so choose each item for a reason. Images must be JPG, PNG or WebP and no larger than 2 MB each. A practical gallery order: 1. Show a clear moment of real gameplay first. Make the genre and player view easy to recognise. 2. Use the next images to explain different mechanics, levels or modes, rather than repeating the same scene. 3. Add a short trailer that shows the game running. Label prototype footage or work-in-progress features honestly. 4. Compare the previews with the build you are distributing. Do not present a planned feature as something buyers already receive. Use Additional Details for the supported platform and genre, where those attributes are available for your category. Put controls and system requirements in the description too. The aim is a page that answers a player's basic questions before they download, without needing a long promotional trailer.

Before uploading a plugin or desktop tool, test the package someone will actually download. In 3DIMLI's Software form, Media & Files accepts one downloadable file, with its size limited by your available storage plan. For a tool with several files, package them together in a supported archive such as ZIP. Here is a simple pre-upload check: 1. Extract the archive into a clean folder and follow the setup from the beginning. Check that required files are included, not just shortcuts to files on your own computer. 2. Include a README with installation, activation and usage instructions. If buyers need a license key, explain where to enter it. 3. Show the actual interface or result in your preview images. A logo alone does not explain how the tool works. You can also add a YouTube or Vimeo demo to the product gallery. 4. Compare the package with the description: supported platforms, dependencies and included files should agree. For an automation script, a small example input and expected output can make the README much easier to follow. Use sample data, not real credentials or customer records. I suggest doing this check before submitting the listing for review, so the first buyer does not have to guess how to begin.

If you offer individual and team licenses for the same plugin, explain the difference before someone buys. In 3DIMLI's Software product form, open License & Pricing. You can start with a Standard, Team, Company or Enterprise template, customize it, or create your own tier. Keep at least one license enabled. For each tier, check these details: 1. Give it a clear name and write the usage terms. Say who may use the software and for what purpose. 2. Use Includes and Restrictions to spell out the boundaries. If you promise support or updates, explain what that covers. Avoid a vague label like "commercial use" when buyers need more detail. 3. Review the price attached to that specific license. A buyer should be able to compare the rights and price without guessing. 4. Compare the listing with the license information and README inside your download package. They should agree. Writing a user or device limit in the terms does not automatically enforce it. If your app needs activation, you can integrate 3DIMLI's purchase verification to identify the purchased license tier. That integration requires an active seller platform plan. Seat counts, device limits and feature access remain your own software or license server's responsibility. A useful final check: could a buyer explain which license they need just by reading the options?

Before sharing a plugin or game purchase link, check the path buyers will actually see. Every 3DIMLI seller store has a public website with product pages, search, cart and checkout. Use Visit Website from your profile menu and review the product page as a visitor. Open the generated Contact, Delivery Policy, Refund & Cancellation, and License Policy pages too. These use the business identity and contact details saved in Store Settings. Check that information and read the pages before sending people there. Need a separate setup guide or launch page? The visual Website Builder lets you create a Page with its own public URL. A Content Block is a reusable section, not a standalone page. Save your changes, then preview the page on mobile and in light and dark appearance before publishing. Keep its URL slug stable once you've shared it. The public store is part of your seller presence. Visual Website Builder editing is a separate add-on. If those controls aren't visible, check Billing > Buy or Upgrade or contact support about your plan. Guide: https://support.3dimli.com/managing-your-dashboard/website-builder

Planning a timed release for a plugin, game or digital pack? Check what happens before and after the purchase window. In 3DIMLI, open the product form's Advance tab and switch on Enable purchase validity period. Choose the start date, time and timezone. If you are starting today, allow at least 15 minutes. A future start keeps the listing visible with a countdown. Buyers can look at the page, but they cannot purchase until that time. Then decide how sales should end: - Set an end date and time if you want new purchases to stop automatically. The product unpublishes at the end. - Select No End Date & Time if you want it to stay available after the start until you manually unpublish it. Existing buyers keep access after unpublishing unless you permanently delete the product. I suggest checking the timezone and viewing the product page before sharing a release time. Explain the purchase window in the description so buyers know when ordering opens and closes.

Adding license activation to a desktop app or plugin? Keep the seller token on your own server. In 3DIMLI, the buyer's Order Item ID acts as the software license key. Here's a practical setup: 1. Open Dashboard > Settings > API Tokens and create a license-verification token. Store it on your license server in a secret manager or environment variable. Never include it in the app. 2. Have the app send the buyer's key to your server. Your server calls POST /api/software/v1/verify with key and product_slug, authenticated with your token. The seller needs an active platform plan, and the token can verify only their own products. 3. After a successful request, check valid before granting access. Map licenseName to the features you want to unlock. Your license terms describe permitted use; seat limits, device tracking and feature access remain your implementation. I suggest testing failure cases before release too. A 401 or 403 can indicate token, ownership or platform-plan trouble. Handle those separately from an invalid purchase. Cache results on your server and recheck periodically. The limit is 30 requests per 60 seconds per IP, shared by buyers routed through the same server. Decide how your app should behave when verification is unreachable. Full request examples and response details: https://support.3dimli.com/creating-products/software/license-verification-api

Shipping the same game for Windows, Mac and Linux? Decide how buyers will choose their build before you publish. In 3DIMLI, open Seller Dashboard > Products, create or edit the product, then enable Variants in the Advanced section. Name each option clearly, such as Windows, Mac or Linux. Open each variant and check its files, price, available licenses and technical details. Each version can have its own download files and media. If you offer an all-platform bundle, say exactly which builds it includes and attach those files to that variant. Choose the default carefully: it is the main purchase option until the buyer selects another one. Keep unfinished builds hidden while you prepare their files. Before publishing, review every visible option: does the name match the package, do the previews describe that version, and are its price and license choices correct? Variants suit versions of the same product. Separate games with different purposes should have separate product pages. A clear choice at checkout starts with a clear file setup.

Should a customer be able to buy the same digital product more than once? For an ebook, template or graphics pack intended as a one-time purchase per customer account, 3DIMLI has a purchase-limit setting. Open the product form's Advance tab, turn on Enable purchase limiting and enter a positive whole number in Purchase limit. A value of 1 allows one purchase per customer account for that specific product. When the account reaches the cap, further purchases of that product are blocked. If customers may need to buy the product again, choose a suitable higher cap or leave limiting off. It's off by default. This cap is per account and per product. It controls repeat purchases; your license terms separately explain what buyers are allowed to do with the files. Sellers remain responsible for enforcing those terms. Before publishing, review the cap alongside your description and license options. Explain any repeat-purchase restriction clearly so buyers can choose the right product and license for their needs.

Before someone buys a plugin or game-development tool, make it easy to check whether it fits their setup. In 3DIMLI's Software product form, open Additional Details. Custom Attributes lets you add up to 10 key-value pairs. Use the space for the supported platform, system requirements and file size. For a plugin, add the host application and versions you've tested. For a game-development tool, describe the compatible engine version and any required dependencies. These are details you supply, so list what you've actually checked. Use precise labels such as "Platform: Windows". If only one build is included, say which one. Put installation and activation steps in the README inside your download package. Before publishing, compare the attributes, description and packaged files. They should describe the same supported setup. This gives buyers a clearer way to decide whether the product is right for them.

One practical tip for selling digital products: choose a page layout around what buyers need to see. In 3DIMLI, go to your seller dashboard, then Settings > Store > Product Page Style. Choose Classic for a compact gallery-and-details layout, or Modern for a tall scrolling gallery with a purchase panel that stays available while people review the product. For a plugin, use screenshots and a clear setup explanation. For a template or graphics pack, show the result and explain which files are included. Put the most useful preview first so buyers don't have to hunt for it. The style saves when you select it and applies across your store's non-booking product pages. Booking products keep their dedicated layout for service, date, time and availability. Then open a published product on desktop and mobile. Check whether the first media items explain what someone is buying and whether the details are easy to follow. Product view counts appear automatically once views are recorded. Use them as an interest signal alongside orders and conversion data when deciding what to improve.

You build a small tool to solve a problem. Maybe it saves you time, handles repetitive work, or makes something easier. Then someone asks, “Can I use it too?” That’s when a different set of questions starts. Where do you upload it? What should you charge? What if one person wants it for themselves and another wants it for their whole team? This is something you can set up on 3DIMLI. From your seller dashboard, choose Software, add your product details and screenshots, and upload your package. It could be a desktop app, plugin, script or developer tool. Add installation instructions and documentation so people know how to use it. You decide what buyers are allowed to do with it. Start with a Standard, Team, Company or Enterprise license template, then edit the terms or create your own tiers. Each license can have its own price. Make it free, set a fixed price, or let buyers pay what they want within the limits you choose. You can also keep different builds or editions under one listing using variants. And if your software needs activation, the buyer’s Order Item ID works as a license key. Your license server can check it through 3DIMLI’s verification API to confirm the purchase and identify the license they bought. You still control feature access and enforce device or seat limits in your software. I want developers to have a clearer way to take something they’ve built and make it available to other people, with their own pricing and usage terms. What have you built that someone else could find useful? Explore 3dimli.com.
More MCP tools →80 free dev tools →
Looking for MCP servers to install? MCP servers list: 289 servers by category, official and community →
3DIMLI is a no-code platform to create branded stores and sell digital products, downloads, services and 3D models.
- for
- Creators, developers and businesses selling digital goods or services online
- pricing
- freemium
Key features
- No-code website builder — Drag-and-drop editor lets anyone publish store pages without coding, with one free page and unlimited with add-on.
- Unlimited product listings — Publish any number of digital items, including 3D models, software, ebooks, audio and more.
- Bulk upload & desktop app — Windows, Mac and Linux app supports watch-folder publishing and bulk product uploads.
- AI-assisted catalog management — AI tools help create, optimize and schedule product listings and variants.
- Interactive 3D viewer — Embed live 3D models from 3DBAE directly on product pages with one-click conversion.
- MCP OAuth integration — Secure OAuth 2.0 MCP server lets AI agents verify licenses and manage store workflows.
Use cases
- Sell 3D models with interactive viewers for designers
- Distribute software or game builds with license-key verification
- Offer consulting, classes or appointments via the booking add-on
- Run a branded storefront for ebooks, audio packs or graphics
- Automate product uploads and promotions using AI and Zapier
3DIMLI pricing
- Flexible$0 to start then 8% of salesPay only when you sell · 5 GB free storage · Unlimited listings · All file types supported
- Fixed Monthly$25/month/month0% platform fee on sales · 5 GB free storage · Priority support · Direct payouts
3DIMLI FAQ
Does 3DIMLI take a cut from my sales?+
On Fixed plans the platform fee is 0%; on Flexible you pay 8% of finalized sales after the month ends.
What happens if I make no sales on the Flexible plan?+
You pay nothing; the Flexible plan only invoices when there are billable sales.
Can I switch between Fixed and Flexible plans?+
Yes, you can change plans anytime from the dashboard; the new plan takes effect at the next billing cycle.
Does the Website Builder work on the free tier?+
Every account includes the no-code builder; you can publish one page and one content block for free, unlimited with the add-on.
How does the affiliate program work?+
Refer creators with your unique link and earn a 20% recurring commission on every plan they subscribe to, as long as they stay subscribed.
Summarized by DevHunt from 3dimli.com · Oct 7, 2026. Details may change; check the official site.











