Help

Frequently asked questions

We answer the questions people ask us most.

General

Cost and license

It's free, and you can change any of the code.

Is Litestore really free?+

Yes. It's MIT licensed, so you can run as many stores as you like, including stores you build for clients.

Do you take a cut of my sales?+

No. Payments go straight to your own Stripe account, and we never see them.

Is there a plugin system?+

Not yet. For now, you add features by changing the code directly.

Hosting

Running your store

Here's what your store needs to run, and how people sign in to it.

What do I need to host it?+

You need somewhere to run Node.js, such as Vercel. The app keeps its data in Postgres and uses Redis for caching. Images go to S3-compatible storage, and Resend sends the email.

Which payment providers can I use?+

Stripe is the only one for now.

How do people sign in?+

They click a link we send by email, so nobody has a password to forget or leak. You can also turn on Google sign-in.

Features

What it can do

Find out what the AI can do and how to bring your store over.

Can the AI change my store on its own?+

No. It fills in forms for you to check or suggests changes for you to approve, and it never moves money by itself.

Do I need an AI key?+

Only if you want the AI features. You bring your own key from Google, Anthropic or OpenAI, and without one the AI buttons stay hidden.

Can I move from Shopify?+

Yes. You can import your catalog straight from your Shopify admin.

Can I sell in more than one currency or language?+

Yes. You set up a market for each place you sell, and each one keeps its own currency, language, tax rules and products.

Which social and ad platforms are supported?+

You can schedule posts to Bluesky and X. Google Ads spend syncs back into the admin, and your products can feed Google Merchant Center and Meta Commerce.

Security

Reporting a problem

If you find a security problem, please tell us privately first.

How do I report a security issue?+

Open a private security advisory on GitHub rather than a public issue, so the problem can be fixed before anyone else hears about it.

Still have a question?

Ask it in GitHub Discussions and we'll get back to you.