Help

With a magic link sent to your email, or with GitHub. There is no password to create or remember. If the link does not arrive within a minute, check spam, then request another.

Pemberley reads your essays and composes your writing profile, then begins assembling your niche: the writers and publications your work is in conversation with. Reading the corpus takes a few minutes; sources appear first and their articles fill in shortly after. Your first issue composes once there is enough to compose from.

If your site has a public RSS or Atom feed, yes, and nearly all blog platforms do. Pemberley reads public feeds only; it does not log in anywhere or bypass paywalls on your behalf.

Yes. Describe the reading you want in your own words during onboarding and Pemberley composes a reading profile from that. When you have a blog, connect it and your profile deepens with your own writing.

It proposes sources from your writing profile: who you cite, who covers your subjects, and who argues with the positions you take. You review the proposals, follow what belongs, and drop what does not. The niche is yours; Pemberley only nominates.

Yes. Add it from your sources page. Feed-less institutional sites are fine too; Pemberley monitors them through news indexing and reads the full articles from the publisher page.

Feeds are checked several times a day, and feed-less sources daily. The latest-writing page and the daily summary reflect what has actually been read, with timestamps where it matters.

Yes. Settings gives you a personal ingest address; set up forwarding from your inbox and each newsletter becomes a private source, readable only by you. Forwarded reading never enters the shared corpus other members are matched against, and only mail that passes sender authentication is accepted.

Set up an automatic forwarding rule in your mail app rather than forwarding each issue by hand. In Gmail that is a filter that forwards matching mail to your ingest address; most other apps have the same. An automatic rule keeps the original sender and list details intact, so each newsletter is filed under its real name and author. A one-off manual forward still works, but it rewrites the sender to your own account, so Pemberley does its best to recover the original from the forwarded message instead.

Every Sunday, by email, with the same issue readable on the web. Your first issue is the exception: it composes right after onboarding, usually within the hour. Recent issues stay available in your archive, and you can pause the Sunday email anytime from settings.

Because the week was quiet. Pemberley would rather send less than send filler, so a thin week is a short issue that says so honestly, never padding.

React to them. “More of this” and “Not for me” are read as signals, and your reading profile is a document you can edit directly: open it, change the prose, and the matching follows. Telling Pemberley what felt off works as well as telling it what landed.

Paste a draft, or a concept as short as a paragraph, and Pemberley returns the conversation it belongs to: who agrees, who argues the other side, what has already been said, and the open angle. Scope it to your niche or to everything Pemberley reads.

Every run autosaves to your workshop history, with the conversation it produced. Reopen a draft to pick up where you left off, or delete it and it is gone.

No. A draft you paste is processed to find its conversation and stored in your own history. It is never published, shown to other members, or added to the reading corpus.

X, Threads, LinkedIn, and Bluesky. Pemberley requests only the permission needed to publish posts you approve, and never reads your timeline, followers, or messages. Where a platform allows it, Pemberley reads the public metrics on posts it published for you, and only those, so the Insights tab can show how they did.

No. Reach drafts posts in your register; nothing goes out until you approve and schedule it. You can review everything queued and pull a post before it publishes.

Platforms expire access tokens, and Pemberley refreshes them automatically where the platform allows. When a platform requires a fresh sign-in, the connection is marked and any scheduled post waits rather than failing silently. Reconnect from your connectors page and the queue resumes.

From your connectors page, one click. Disconnecting deletes the stored token immediately. You can also revoke access from the platform side.

Intelligence, your weekly issue, is $10 a month or $100 a year (two months free). Reach, the optional auto-posting add-on, is $30 a month or $300 a year on top. A card is required at signup and billing is handled by Stripe.

No. Your card is charged when you subscribe, and onboarding begins right after. Cancel anytime, no questions asked; your access runs to the end of the period you paid for.

From settings. You can add or remove Reach and switch between monthly and annual there; the Cancel option opens Stripe’s billing portal. Cancellation takes effect at the end of the period you paid for; nothing renews after that.

Email jamie@born2be.io and it is done. The privacy policy covers exactly what is kept and for how long.

A few of the heavier tools, like Contextualize runs, have per-day limits to keep the service fast and sustainable for everyone. Limits reset daily. If one is genuinely in your way, say so.