webbysol: publishing a website for one payment

1. The problem

Website builders are priced as though every site is a business that will still exist in three years. The first ten minutes are free and pleasant. The bill arrives monthly, forever, and it is charged for continuing to exist rather than for anything further being done.

That model fits a law firm. It fits a restaurant. It fits almost nothing in the space webbysol was built for, where a project may be assembled in an afternoon, may need a page online within the hour, and may be finished or transformed within a month. Charging rent on a page like that produces two bad outcomes: the site is taken down when the card fails, or it is never built at all because a monthly commitment is the wrong shape for the thing being announced.

There is a second problem underneath the first. A subscription builder holds the site hostage to keep collecting. The natural consequence is that editing, exporting and even continued hosting are all bundled into the recurring fee, and a lapsed payment takes the work with it. The site is rented, not owned, and the tenant discovers this at the worst moment.

2. Design principles

Four commitments shape every decision in the product. They are stated here so they can be checked against what the software actually does.

• Building is free and stays free. The full editor, every block, every theme control and every one of the 15 templates are available before any payment. Nothing is demonstrated and then locked.
• Publishing is a single payment. There is no subscription, no renewal and no expiry. A published site does not stop working because time has passed.
• Editing after publishing is free forever. This is the commitment the subscription model exists to prevent, and it is the one that matters most: the payment buys publication, not access to your own work.
• The platform never takes custody of funds. Payments settle on Solana from a wallet the user controls, and the keys are exportable at any time.

3. How a site is made

The path from nothing to a live site is four steps, and the first three cost nothing.

• Choose a template. There are 15, ranging from a narrative editorial scroll to a brutalist receipt to a working handheld console. All of them can be browsed in full before signing in.
• Edit it. Blocks can be added, deleted, duplicated, reordered and hidden. Colour, type, spacing, radius, texture and motion are all under direct control, with a raw CSS field for anything the controls do not reach.
• Optionally paste a contract address, which fills in a large amount of the site automatically. This step is genuinely optional; a site with no token works exactly as well.
• Publish. The site goes live on a subdomain immediately, and a custom domain can be attached at any point afterwards.

The order is deliberate. A visitor can reach the end of step two, with a finished site on screen, before being asked for anything at all.

4. The block system

A webbysol site is an ordered list of blocks. A block is a self-contained section with its own fields: a hero, a stat grid, a story chapter, a roadmap, a gallery, an FAQ, a contract address panel, a button row, a footer. Roughly thirty exist.

A template is not a fixed design. It is an arrangement of blocks plus a theme, and both halves remain fully editable after it is chosen. This has a consequence worth stating explicitly: switching template does not discard the work. The Design tab offers a template swap that moves all existing blocks and copy onto a different look, so a decision made in the first minute is never a decision the site is stuck with.

Blocks are also how the pricing tiers are drawn, described in section 10.

5. Live data from a contract address

Pasting a Solana contract address into a draft does more than switch on a price ticker. The site is filled in from what is publicly known about the token: its name and ticker wherever the template left a placeholder, total supply, a live chart, and the project's own links, including X, Telegram, the launchpad page, an aggregator swap link and a block explorer. Price, market cap, volume and liquidity then update on their own.

There is no API key to obtain and no additional charge; live data is part of the one-off price.

One rule governs all of it, and it is the rule that makes the feature safe to use on a site somebody has already written:

Autofill only ever fills a blank. Anything a person has written or set themselves is never overwritten.

A heading that has been edited stays edited. A social link that has been set by hand stays set. A site name that has been chosen is not renamed to match the token. The feature is designed around the assumption that it will frequently be used after the site has been written rather than before, because that is what people actually do.

6. Launching a coin

The previous section describes a site that already has a contract address. This one describes the other case, which until recently meant leaving the platform: a finished site for a coin that does not exist yet.

A site built here already holds everything a coin needs. The name and ticker were chosen before the editor opened, the description was written for search, the logo sits at the top of the page and the project's own links are in the footer. So the launcher reads them rather than asking for them again. Nothing is retyped and nothing is pasted between two places, which is where the details in this process are normally lost.

The coin is created on one of two launchpads, chosen by the owner on the launch screen: pump.fun, through their own published SDK, or StonkFun, on the Raydium LaunchLab programme that their platform runs. On either, the creation and the creator's first purchase are a single transaction. That the two are one transaction is the substantive part rather than a detail of implementation: there is no moment in which the coin exists and its creator has not bought, so the first purchase cannot be placed in front of. Splitting them, which is the simpler thing to build, would hand that position to anybody watching.

• The creator is the site owner's own wallet, always, and the platform never takes any part of what that creator earns. Both launchpads pay the creator a share of the trading fees on their coin for as long as it trades: pump.fun on a schedule of its own that declines as the coin grows, StonkFun as half of the one per cent its pool charges, forwarded to the wallet as it is earned. On either, the owner may instead direct that share to the people holding the coin, who are then paid it in proportion to what they hold; on StonkFun this takes the form of a transfer tax of one or three per cent. Either choice is fixed when the coin is created and cannot be revised afterwards.
• A coin is normally priced in SOL and can instead be priced in another token that the chosen launchpad accepts as a quote, including tokenised shares in listed companies. A coin priced that way has its chart and its market value denominated in that token rather than in SOL, and the creator's share of its trading fees is paid in the same token.
• The mint key is generated in the owner's browser and never leaves it, so the platform is not in a position to create anybody's coin, before them or otherwise.
• The first purchase is optional and can be nothing at all.
• A platform fee is charged alongside the cost of creation itself, which is pump.fun's own charge on one launchpad and the network's rent for the coin's accounts on the other, shown as one figure before anything is signed. It is a quarter of that cost or a fixed floor, whichever is greater, and it exists to cover the network costs of running the service rather than to profit from a launch.

The contract address is written back into the site as soon as the coin is confirmed on-chain, at which point every part of the previous section applies to it: the price, the chart, the market data and the buy links all begin working without further editing. A launch that does not confirm is reported as a failure and creates nothing, and a site can only ever produce one coin.

The launcher is offered only to sites that have no contract address, and it is opened deliberately rather than put in front of somebody finishing something else. Publishing a website and creating a token are separate decisions and only one of them is permanent, so the second is never the consequence of the first. A site built to revive an existing token is not a site that wants a new one either, and offering it there would be a mistake with permanent consequences.

7. Payments and custody

Publishing is paid in SOL or USDC on Solana. Two routes exist: paying from an existing wallet by scanning a Solana Pay request, or paying from a wallet created during sign-in.

The second route deserves explanation, because it is where most misunderstandings about custody arise. Signing in with a Google account creates a Solana wallet held under keys the user controls, not keys the platform holds. The private key can be exported at any time, and the wallet continues to exist and function independently of webbysol. The platform cannot move funds it does not hold, and this is a property of how the wallet is constructed rather than a promise about how it will be operated.

Payments are verified on-chain before a site is marked as published. The address every payment settles to is published on the site itself, so the flow of funds is auditable by anyone who cares to look, without asking.

8. Ownership, visibility and control

A published site is controlled by its owner along several independent axes, each of which is reversible and free to change.

• Live or switched off. A site can be taken offline and put back without unpublishing it or paying again. When it is off, visitors see a notice styled in the site's own colours rather than a broken page or a platform error.
• Listed or unlisted. A live site can be excluded from the platform's public showcase, so that a project can be online and shareable by link without being announced anywhere. This is offered at the moment of publishing as well as in the site's settings, because that is when the decision is actually being made.
• Domain. Sites are published on a free subdomain and a custom domain can be attached whenever the owner has one.
• Analytics. Each site reports its own traffic to its owner and to nobody else.

9. Languages

The entire product is available in English, Spanish, Chinese, Korean, Russian, Turkish and Vietnamese. This covers the whole interface rather than the marketing pages alone: the editor, every block name and field label, the wallet, the checkout and the legal pages are all translated.

The reasoning is narrow and practical. Walking somebody through a wallet screen in a language they do not read is where a great deal of onboarding fails, and it fails silently, because the person simply leaves. Language selection persists and every subsequent screen follows it.

Legal documents are translated as a convenience and the English versions govern, which each translated page states at the top.

10. Trust, moderation and copyright

A platform that lets anybody publish a page in five minutes has obligations, and pretending otherwise is not a strategy.

webbysol operates a notice-and-takedown process with a registered copyright agent, reachable at the address published on the support and copyright pages. Reports can be filed by anyone, and a removal can be contested by the person whose material was removed.

Known infringing material is blocked at upload by content hash. Beyond that, the approach is deliberately to flag rather than to block: automated systems that refuse uploads outright produce false positives that fall hardest on legitimate users, and a queue reviewed by a person is more accurate than a filter that cannot be argued with.

Every published site carries the disclaimers required of it, and nothing on the platform constitutes financial advice.

11. Pricing

Two tiers, both one-off, both covering unlimited editing afterwards.

• Standard, ten dollars. 9 of the 15 templates.
• Premium, twenty dollars. The remaining 6.

The line between them is a rule rather than a judgement: a template is premium if it ships an advanced block, such as a full-screen splash gate or a video wall. Anything available to every template as a free toggle is deliberately excluded from that test, because a Standard buyer can already switch those on and so they cannot be what the extra ten dollars buys. The advanced blocks are visible in the previews before purchase, so the difference can be seen rather than taken on trust.

A referral programme pays twenty-five dollars for every ten sites published by people who signed up through a given link. It counts published sites rather than signups, which is the only version of such a programme that cannot be farmed.

12. The token

webbysol has an associated token, Webbysol, ticker WSOL, on Solana. It was launched publicly on pump.fun with no presale, no private round and no allocation reserved for anyone before the market opened. Its full details are below and every one of them can be checked on-chain rather than taken from this document.

• Network: Solana
• Contract address: 61Do8JA4hnR33WBhexGvH5XKcwPMM3D221xHmgTCpump
• Total supply: 1,000,000,000 WSOL, six decimals
• Circulating supply: 1,000,000,000. The full supply is in circulation; none is locked, vested or held back.
• Mint authority: revoked. No further tokens can ever be created.
• Freeze authority: revoked. No holder's tokens can be frozen.

The two revoked authorities are the substantive part. Together they mean the supply figure above is permanent and that no account, including any operated by webbysol, can interfere with a holder's balance. Both are readable directly from the mint account on any Solana explorer.

The token's relationship to the platform is deliberately limited, and it is worth being exact about it, since projects in this space routinely are not. The token is a community asset. It does not confer equity, revenue share, governance rights, or any claim on the platform or its earnings. Publishing does not require it; the product is priced in dollars and paid in SOL or USDC. Nothing about the platform's operation depends on the token's price, and no part of this document should be read as a projection of its value.

13. What webbysol is not

Stating the boundaries is more useful than implying there are none.

• It does not issue, sell or distribute tokens. Section 6 describes a launcher that assembles a coin from a finished site and creates it on pump.fun or StonkFun, and the distinction matters: the coin is created by its owner's wallet, on somebody else's market, with the owner as its creator throughout. The platform builds the transaction and the owner signs it. Nothing is issued by webbysol, held by webbysol, or sold on its behalf.
• It does not make a market in anybody's token, and it does not trade them. The first purchase a creator makes is their own, in their own wallet, and the platform holds no position in any coin launched through it.
• It is not a financial service and nothing it publishes is financial advice. Live market data is displayed as read from public sources and is not a recommendation.
• It does not run arbitrary code on a customer's behalf. Sites are composed of blocks and styling, not of uploaded applications.
• It does not promise an audience. Publishing puts a page online; the traffic that reaches it is the owner's work, not the platform's.
• It does not hold funds, and therefore cannot recover them. A wallet whose exported key is lost is lost, in the same way any self-custodied wallet is.

14. Direction

Deliberately undated, because a roadmap with dates on it is a set of promises made by somebody who cannot yet know the answer.

The block catalogue continues to grow, and new blocks are added to every existing site rather than to new sites alone, since a site that was published last month is still being edited this month. Template work continues on the same basis. Beyond that, the areas under active development are richer direct manipulation inside the editor, broader language coverage, and reducing the number of placeholder fields a new site ships with, which is currently the single largest source of unfinished-looking published sites.