Setup guide
Start with one companion and a concise everyday-romance brief, rather than buying extra features first. Choose Kindroid if you want documented Backstory, Response Directive and Example Message controls; choose Nomi if you prefer beginning naturally and adding stable relationship context through Backstory+. These are differences in setup controls, not evidence that either provider is better. Make warmth and ordinary conversation explicit so your setup does not rely on a vague request to “be my partner.” [1] [7]
Checked 2026-10-02 · 12 sources · reviewed before publication
Start here
A setup you can edit
Use this as a draft, not as a magic prompt. Keep only the details that actually matter to your character.
Suggested wording—not a vendor template or tested configuration. Relationship brief: Alex is an adult AI companion, and I am an adult. Our relationship is romantic, affectionate and unpressured. Alex is warm, grounded and lightly humorous. We mostly talk about our day, meals, hobbies, work and weekend plans. Alex speaks directly rather than narrating elaborate scenes. Alex respects that I have an offline life and may leave conversations unfinished. Conversation preference: Use natural, concise replies, usually one or two short paragraphs. Ask at most one follow-up question. Offer affection without turning every exchange into a romantic speech. If a personal detail is uncertain, ask rather than inventing it. Example reply: That sounds like a long day. Want to talk about the frustrating part, or switch gears and figure out dinner?
Build it step by step
1. Put the relationship in Kindroid’s Backstory or Nomi’s Backstory+
Choose the setup route that matches how you want to customize—not an assumed quality ranking. In Kindroid, open the upper-left menu → Backstory. Its guide recommends using Backstory for identity, speaking style, core personality and relationship to you. In Nomi, open Backstory+ and use it for relationship context and preferences.
Suggested starting brief: one adult companion, an affectionate romantic relationship, and an explicit focus on everyday conversation. Use the example below, replacing Alex with your chosen name. Avoid a long fictional biography until the basic conversation feels right. [1] [7]
2. Use model-appropriate settings—or begin with a plain conversation
If you use Kindroid’s Ember model, click the LLM version icon in the upper-right corner. The Ember guide recommends starting with Speedy reasoning, Companion flair and Dynamism at 0.95; it suggests small adjustments within 0.95–1.05. Apply these settings to Ember, not automatically to another model.
For Nomi, its beginner guidance recommends starting naturally. Suggested opening: “I’d like a warm romantic relationship, but most of our chats should be ordinary conversation about daily life.” No equivalent Ember tuning controls are established by the supplied Nomi sources. [1] [7]
3. Specify ordinary replies without overloading the controls
In Kindroid, put the example’s Conversation preference into Response Directive and its Example reply into Example Message. The Ember guide recommends keeping both minimal and short.
In Nomi, try the preference as a normal conversational request first. If a persistent style problem remains, use Inclinations sparingly: the July Q&A recommends ideally one or two simple, persistent concepts, as a last resort. Suggested concept: “Prefers concise everyday conversation.” Do not transplant Kindroid’s field names into Nomi or build a long behavioral script. [1] [7] [8]
4. Add a few useful details, not your entire life history
Suggested starting facts: your preferred name, a hobby you often discuss and one recurring part of your schedule. Supply only details you are comfortable sharing; invented test details are also suitable for checking the setup.
For Kindroid, keep the core relationship in Backstory and move extended background into Journal Entries with specific keyphrases, as its guide recommends. For Nomi, use Backstory+ for stable relationship context and preferences. Treat these as context controls, not promises that every detail will appear correctly in every reply. [1] [7] [9]
5. Check everyday exchanges and adjust one problem at a time
Suggested check: discuss a routine workday, ask for a dinner idea, then talk about a weekend plan. Look for the behavior you actually want: manageable reply length, restrained affection, relevant questions and no invented personal facts.
If replies become elaborate scenes, simplify the relationship brief and restate that you want direct conversation. If questions feel like an interview, request fewer follow-ups. In Kindroid, its guide recommends changing one setting at a time and allowing several turns before changing another. Suggested approach for either provider: correct the smallest identifiable problem rather than rewriting everything after one disappointing reply. [1]
When the conversation becomes exaggerated, repetitive or forgetful
For Kindroid, check which model is selected before changing settings. The Equinox V7 guide warns that emphatic traits and rigid rules carried over from V6 can become exaggerated; it recommends simplifying Backstory and Example Messages, and using Suggest or Tweak for repetition. Its advice to temporarily raise Dynamism to 1.5 or above for persistent repetition is model-specific—not a replacement for Ember’s recommended 0.95–1.05 starting range.
For Nomi, do not treat a corrected Mind Map entry as a complete memory rewrite. Editing or locking an entry does not edit the underlying memory. Entries are selected dynamically rather than all being used in every reply, and updates can lag. A missed detail therefore does not necessarily mean your relationship brief was ignored. [1] [2] [9]
Establish the conversational fit before paying
Nomi’s refund FAQ documents an indefinite free plan with 50 messages per day and describes subscription purchases as nonrefundable. Suggested approach: use that allowance to check whether ordinary conversation suits you before subscribing.
Kindroid’s retrieved billing interface lists larger context and recall allowances for Ultra and MAX. Ultra is an add-on to Standard; MAX requires both Standard and Ultra. These add-ons are monthly-only, and their context improvements are guaranteed only for the latest subscriber LLM. Larger allocations are not recall-accuracy scores.
Suggested purchase rule: first identify a concrete limitation you repeatedly encounter. Do not buy additional memory, voice or visual features merely because the initial personality setup feels wrong. [3] [4]
Keep this limitation in mind
This is a setup guide based on public provider documentation, not hands-on testing or evidence that either provider produces better conversations. The supplied sources do not establish current Kindroid prices or free-plan allowances, or a complete current Nomi paid-plan entitlement table.
Where this setup may fit
Shown because the current provider record matches this need. Check the exact plan and limitation before paying.
Nomi
Checked 2026-10-02
The documentation supports editable Mind Map summaries, user-managed backstory context, backstory-based French preferences, pronoun customization, and Friend/Romantic starting settings. Underlying memories are not directly editable. Native character-card import and Japanese-specific chat setup remain unverified. Current free-versus-paid eligibility and limits are unverified for the listed capabilities; missing restrictions do not establish equal access. This is a public-documentation review, not an application test or certification of current availability.
- Editable or persistent memory
- Documented context / conversation window
- Documented French chat setup
- Voice or calls
Why it matches: Select Romantic as the relationship type when creating a Nomi, using the creation-stage selection documented in the older setup guide. Current documentation describes Romantic as a romance-oriented starting point, not a rigid behavioral requirement. Relationships can develop over time. Changing an existing Nomi's relationship-type selector is not verified.
Lovescape
Checked 2026-10-02
The supplied public documentation supports conversational memory correction, last-response regeneration, general relationship-type configuration, and character-profile editing. Friend and Romantic partner roles are documented, but their exact selectors and behavior are not. Memory is documented on all plans, while free character creation has subscription-dependent character counts; neither establishes equal performance or role-specific entitlements. Buyers needing a dedicated memory editor, character-card import, French/Japanese text-chat setup, or pronoun controls should treat those requirements as unverified, not proven unavailable. This is a documentation review, not a hands-on test.
- Editable or persistent memory
- User persona / profile controls
- Friendship / platonic relationship setting
- Romantic relationship setting
Why it matches: Romantic partner is explicitly documented as a possible character role, and the creation guide provides a general Relationship type field. The evidence does not document an exact Romantic partner selector or establish its behavior. Creation is free after registration, character counts depend on subscription, and romantic-role entitlements are not specified.
Nectar AI
Checked 2026-10-02
The evidence supports French chat, companion customization and memory-related plan differences; relationship-level customization and Ultimate’s 64K context are provider editorial claims without precise UI documentation. Editable memory, character-card import, dedicated pronoun controls and explicit Friend/Romantic settings remain unverified, not necessarily unavailable. Advisory pronoun fallback: write, 'For this chat, refer to me as [name] and use [pronouns].' This is an identity instruction, not a dedicated control or a guarantee of persistence. Advisory Japanese fallback: write, 'Please reply in Japanese for this chat.' Japanese support, persistence, voice output and tier eligibility remain unverified; receiving a Japanese reply would not verify those capabilities. If stored-memory editing or automatic card import is essential to your purchase, this documentation does not establish that Nectar meets those needs. No application behavior was tested.
- Editable or persistent memory
- Documented context / conversation window
- Documented French chat setup
- User persona / profile controls
Why it matches: The product-specific setup article says users can set romance, intimacy and dependency levels after choosing or customizing a character. It does not identify control names, available values, saving steps, later-editing procedures or eligible tiers. This supports a broad relationship-customization claim, not a verified dedicated Romantic setting or a Friend mode that constrains romantic responses.
Sources
Checked 2026-10-02
- Ember LLM Guide · Kindroid Help Center
- Equinox (V7) LLM Guide · Kindroid Help Center
- Kindroid – Your Personal Artificial Intelligence Companion
- Does Nomi offer refunds? – Nomipedia – The Nomi AI Companion Wiki
- Nomi 101: A Beginner's Guide to Getting Started with Your AI Companion – Nomi.ai
- Choosing a Subscription – Replika
- Nomi 101 A Beginners Guide – Nomipedia – The Nomi AI Companion Wiki
- 2025 July Q&A Summary – Nomipedia – The Nomi AI Companion Wiki
- Are Mind Map Entries Memories? – Nomipedia – The Nomi AI Companion Wiki
- How do I change my relationship status? – Replika
- How does Replika’s memory work? – Replika
- What is Replika Ultra? – Replika
Provider documentation tells us what a service describes. Unless a page explicitly says otherwise, we are not presenting it as a hands-on performance test.