Can Sentway serve my page on my own domain?

Not today. Published sites are served on their own subdomain of sentway.page. If a custom domain is essential, ShareDuo supports one and Sentway does not.

Yes. Nothing stops you sharing quick artifacts one way and publishing the pages that need responses, access rules or payment through Sentway.

Comparison

Sentway and ShareDuo

ShareDuo is genuinely good at getting a Claude artifact out as a controlled link quickly, with password protection, expiry, search engine controls, view analytics, custom domains and an MCP server of its own. Sentway is shaped around what happens after the page is open: responses captured natively, visitor activity recorded, results queried by the connected AI over MCP, several pages published as one site, and paid access handled end to end through your own Stripe account.

What ShareDuo is good at

Turning a Claude artifact into a shareable link quickly
Link controls such as password protection, expiry and search engine visibility
Invite-only email access on its paid product, plus view analytics
Custom domains, which Sentway does not currently offer
An MCP server for uploading, listing, fetching and updating shared content

Nothing below is a criticism of that. Sentway is shaped around a different job, and the table sets out where the two differ.

The difference in one line

ShareDuo is centred on sharing an artifact with controls around the link. Sentway is centred on the record the page produces: who visited, what they submitted, what they completed, and what they paid for.

Both connect to an AI over MCP, but they expose different things. ShareDuo's MCP surface covers uploading, listing, fetching, updating content and settings, and deleting; its own MCP page lists analytics queries and invite management as future roadmap items. Sentway's MCP surface includes reading submissions, visitor activity, analytics and paid access state back into the conversation.

Collecting responses

ShareDuo's own artifact examples guide is clear that interactive forms and surveys have no backend by default, and that production response collection needs a real submission target such as Formspree, a webhook or an embedded form service.

In Sentway that part is built in. Form fields with name attributes are captured as the visitor submits them, stored against the site, and read back by your AI. There is no endpoint to configure and no third-party form service in the loop.

get_submissionsFree plan
list_worksheet_answersPro: Visitor worksheet history
list_visitor_uploadsPro: Visitor uploads

Knowing what happened

Sentway records each visitor as a record rather than as a view count: visits, active time, answers given, tasks completed and uploads left behind. Your AI queries that directly in the conversation that produced the page.

get_analyticsFree plan
list_visitorsPro: Visitor timelines
get_visitor_activityPro: Visitor timelines
list_plan_progressPro: Visitor timelines

Sites and paid access

A Sentway site can hold several pages published together as one atomic snapshot, so a proposal, an appendix and a next steps page arrive as one thing.

Paid Access puts a price on a site or on specific paths. Payment runs through your own connected Stripe account and Sentway grants the buyer an entitlement to the protected content once it succeeds.

get_paid_accessFree plan
set_paid_accessPro: Paid Access
get_commerce_setupFree plan

Side by side

How Sentway and ShareDuo differ in shape. Neither column is a score.
Capability	Sentway	ShareDuo
Main job	Publishing and measuring pages an AI produced	Sharing Claude artifacts with controls on the link
Form responses	Captured natively and stored per site	Its guide points to a submission target such as Formspree, a webhook or an embedded form service
Visitor record	Per visitor visits, active time, answers, uploads and completed tasks	View analytics
MCP surface	Authoring plus reading submissions, visitors, analytics and paid access	Upload, list, get, update content, update settings and delete, with analytics and invite management listed as roadmap
Access control	Public, email capture, verified email, allowlist or password, checked on the server	Public links, password protection, expiry, and invite-only email access on the paid product
Multiple pages	Several pages published together as one site	Shared artifacts
Charging for access	Paid Access with your own connected Stripe account and entitlements	Not part of the sharing flow
Custom domain	Not available. Sites are served on a subdomain of sentway.page	Custom domains supported

Which one to reach for

Use ShareDuo when

You want the quickest controlled share link for a Claude artifact and nothing more.
The page has to sit on your own custom domain, which Sentway does not currently support.
Link controls such as password, expiry and search engine visibility are the whole requirement.

Use Sentway when

The page collects answers and you want them stored without wiring up a form service.
You want your AI to tell you who visited, what they answered and what they finished.
You are publishing several pages as one site, or charging for access to them.

Try Sentway free

Questions people ask

Can Sentway serve my page on my own domain?: Not today. Published sites are served on their own subdomain of sentway.page. If a custom domain is essential, ShareDuo supports one and Sentway does not.
Do I need a form service to collect answers in Sentway?: No. Fields with name attributes are captured as the visitor submits them, stored against the site, and read back by your AI over MCP.
Can I use both?: Yes. Nothing stops you sharing quick artifacts one way and publishing the pages that need responses, access rules or payment through Sentway.