Why we built our own platform: an honest look

Choosing where your website lives is one of those decisions that feels straightforward until you're deep into it. The comparison charts blur together, the pricing is never apples-to-apples, and every platform's marketing tells you the same story: we're the best, trust us.

We're in an unusual position to write about this, because we've been on both sides of it. For years Tropic Arts built premium themes for other people's platforms. We shipped themes, supported the merchants who bought them, and watched what happened to those stores over the following years. Now we build and run our own platform, and the sites we design run on it.

This article is an attempt to be honest about why we made that move, what it genuinely does better, where it falls short, and how to tell whether it's the right foundation for you. It is not a claim that we've solved something nobody else has.

What ten years of building themes taught us

A theme is a beautiful thing to sell and a frustrating thing to own. We would spend months on a design — the weight of a typeface, the rhythm of a product grid, the way a page settles as you scroll — and then hand it to a merchant who had to assemble the rest of their business around it themselves.

And they did assemble it. Almost every store we supported ended up in roughly the same shape: the platform subscription, a separate email tool, a reviews app, a booking app, a page builder, a form builder, sometimes a subscriptions app, and a handful of small utilities nobody quite remembered installing. Each one billed separately. Each one loaded its own scripts onto the storefront. Each one updated on its own schedule, and had its own opinion about how a page should look.

The result was a store that looked like our theme on the home page and looked like a committee everywhere else. Support tickets stopped being about the theme and started being about the seams — the review widget in the wrong font, the booking form that redirected to a page with somebody else's branding, the page builder that quietly overrode our spacing.

We could control the quality of a theme. We could not control the quality of the site it ended up inside.

That's the gap that eventually pushed us to build a platform rather than another theme. Not because the platforms we worked on were bad — they weren't, and we'd still recommend the big ones for the businesses they suit — but because the thing a merchant actually needs is a whole site that holds together, and a theme can only ever be one part of that.

What we built instead

Tropic Arts is now a platform: templates, a visual editor, hosting, a store, bookings, a blog, email, a customer list, and a domain, in one account with one bill. Three ideas shaped it, and they're worth naming because they explain most of the trade-offs further down.

One render path

The editor and the published page run the same code. When you drag a section into place, you're not looking at an approximation of the result — you're looking at the component that will render for your visitors, with your content in it. There is no separate “preview mode” that can drift out of sync with what publishes, because there's only one thing to keep in sync.

Everything in the same box

Your products, your bookings, your blog posts, your contacts and your locations are all first-class records on the same platform as your pages. A booking form writes to your contact list. A product block on the home page reads live inventory. A section that lists your locations updates when you edit an address. Nothing has to be synced between tools, because there aren't separate tools.

Design as a system, not a skin

Every template is built from the same shared blocks and the same design tokens. Set your brand colors once and buttons, links, headings and highlights follow across every page — and into your newsletters, which pick up the same palette. It's the difference between a site that's been decorated and a site that's been designed.

What it does well

There's nothing to install, and nothing to patch

Hosting, SSL, daily backups, a global CDN, and unlimited pages and bandwidth come with every plan. There are no servers to provision, no security updates to chase, and no plugin compatibility matrix to reason about. That whole category of work simply isn't yours — which was the single biggest thing merchants told us they wanted back.

The store is part of the site, not bolted to it

On the Store plan you get products and inventory, categories and filters, a slide-out cart, Stripe checkout, orders and fulfillment, refunds, shipping rates, sales tax, in-store pickup, subscriptions and customer reviews. All of it renders in your template's fonts and colors, because it's built from the same components as the rest of your site. A shopper never crosses a visual seam between “the website” and “the shop.”

You can build the entire thing before you pay

The free Trial isn't a stripped demo on a countdown. You get the real editor, the real templates, the blog, appointments and the customer list, and you can build and preview your whole site. What the Trial can't do is publish to the world or send marketing email — those come with a paid plan. You decide whether it's worth $29 or $39 a month after you've seen your own site, not before.

Every template is included, always

There are no template fees and no premium tier of designs. Every template in the catalog is available on every plan, including the Trial, and you can move an existing site onto a different one without starting over. We'd rather you found the design that actually fits than picked the one you'd already paid for.

Your data stays yours

Customers, products, categories, locations, appointments and booking forms all import and export as CSV, and an entire site — pages, content and settings — exports as a single bundle. There's a privacy-policy and DPA generator, GDPR request tooling, cookie consent, and two-factor authentication on every plan. Leaving should be possible; that's a feature, not an oversight.

Where it falls short

No platform is without trade-offs, and ours are real. Here they are.

We're younger than the alternatives

The large platforms have been hardened by millions of stores over more than a decade. We haven't. Our catalog is measured in dozens of templates, not thousands. If you want the reassurance of the biggest possible ecosystem and the longest possible track record, that's a legitimate reason to choose someone else, and we'd rather say so plainly than pretend the difference doesn't exist.

There's no app store

This is the direct cost of the all-in-one design. If you need a capability we haven't built — a niche loyalty scheme, a specific 3PL integration, a particular accounting sync — you can't install your way to it. You ask us, and you wait. On a platform with an app marketplace, someone has usually already built it. That's a genuine advantage of that model and we won't argue otherwise.

What we'd say in return is that the trade runs both directions: the reason your site can't sprout a badly-styled third-party widget is the same reason you can't install one.

It's opinionated

Pages are built from our blocks. Checkout runs through Stripe. The data model has particular ideas about what a product, a category and a booking are. For most businesses those opinions save time. If your business genuinely doesn't fit them — an unusual product structure, a bespoke checkout, deep integration with proprietary systems — you will feel the walls, and you'll feel them sooner than you would on a more open stack.

You're depending on us

This is the honest core of it. Building on a managed platform means trusting the people who run it — our uptime, our roadmap, our judgment about what to build next, and our continued existence. We think that's a fair trade for everything above, and we've tried to make it a smaller bet by keeping your data exportable and your domain yours. But it is a bet, and you should make it with your eyes open.

Who it's right for — and who it isn't

Tropic Arts fits businesses that want a site that looks considered and stays that way without becoming a project. Small retailers and makers, studios and practices, trades and home services, restaurants and cafés, photographers and consultants — people who would rather spend their evenings on the work than on plugin compatibility. It fits especially well if you want a website, a store, bookings and an email list to feel like one thing rather than four.

It's a poor fit if you have unusual technical requirements that sit outside our data model, if you depend on a specific third-party integration we don't offer, if you have an engineering team that genuinely wants control of the whole stack, or if you're running at a volume where shaving a fraction of a percent off transaction costs is a real line item.

And if you're already on a big platform, running well, with a stack that isn't fighting you — stay. Migration has a cost and “it's nicer” rarely covers it. The case for moving is strongest when you're about to rebuild anyway, or when the seams have started costing you more than the subscriptions do.

---

Choosing a foundation, not just a feature set

When you choose a platform, you're not just choosing where your pages live. You're choosing who's responsible for your security and your uptime, how many bills arrive each month, how many logins you keep track of, and how much of your attention the thing consumes when it isn't actively earning you anything.

We built this because we got tired of designing one beautiful part of something that was, taken as a whole, held together with tape. We wanted the store to look like the site. We wanted the booking form to be in the same typeface as the page it sits on. We wanted a merchant to be able to change their mind about a design without paying for it twice.

That's what a good foundation does. It doesn't ask for your attention. It just works, quietly, so you can spend your time on everything else.