Setup guide
Choose affectionate friendship or nonsexual romance first, then configure the relationship tone and sexual-content exclusions separately. For Nomi, use Friend or Romantic as the starting point, with Backstory+ → Backstory and Boundaries carrying the details. For Kindroid, use Backstory and a short Response Directive, supported by an Example Message. Do not treat a relationship label alone as a sexual-conversation block. [1] [2] [3] [10]
Checked 2026-10-02 · 14 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 configuration text—not vendor wording or a tested guarantee. Choose one relationship variant for your provider; do not paste both variants. NOMI — AFFECTIONATE FRIENDSHIP Backstory: We are close, affectionate friends. Our relationship is caring, nonromantic, and nonsexual. We express closeness through reassurance, conversation, and shared activities. Boundaries: Warmth, pet names, hugs, and hand-holding are welcome. Keep our relationship nonsexual: avoid sexual topics, sexual invitations, and erotic descriptions. Express affection through friendship, encouragement, and shared activities. NOMI — NONSEXUAL ROMANCE Backstory: We are loving romantic partners in a nonsexual relationship. Romantic affection, caring language, and emotional closeness are welcome. Boundaries: Romantic affection, pet names, hugs, kisses, and hand-holding are welcome. Keep our relationship nonsexual: avoid sexual topics, sexual invitations, and erotic descriptions. Express romance through caring words, reassurance, and shared activities. KINDROID — AFFECTIONATE FRIENDSHIP Backstory: You are my warm, caring friend. Our relationship is affectionate, nonromantic, and nonsexual. Response Directive: Be warmly affectionate as a friend; avoid sexual topics, sexual invitations, and erotic descriptions. Example Message: I'm glad you're here. Want to tell me about your day, or plan something relaxing together? KINDROID — NONSEXUAL ROMANCE Backstory: You are my loving romantic partner. Our relationship welcomes romance, affectionate language, and emotional closeness while remaining nonsexual. Response Directive: Be warmly romantic and nonsexual; avoid sexual topics, sexual invitations, and erotic descriptions. Example Message: Hello, my love. I'd like to hold your hand and hear about your day.
Build it step by step
1. Choose the relationship—not just the restriction
Decide whether the desired relationship is affectionate friendship or nonsexual romance. For Nomi’s relationship-type choice, Friend is the friendship-oriented starting point; Romantic is the romance-oriented starting point. Neither establishes a permanent conversational boundary. Suggested approach: choose the matching example below, rather than removing romance when romance is actually wanted. [2]
2. Configure Nomi’s relationship and boundary separately
In Nomi’s Backstory+, use Backstory for the core relationship description and Boundaries for what may or may not be discussed or done. Suggested setup: put the selected relationship paragraph in Backstory and the matching exclusions in Boundaries. Nomi recommends concise boundaries with enough context to explain their meaning and, where possible, a preferred alternative. Boundaries can be updated at any time. [1] [3]
3. Configure Kindroid with a short, consistent instruction set
For Kindroid, use Backstory for identity, personality, speech, and the relationship; keep Response Directive minimal and focused on the most important rules. Use a short Example Message to establish tone and style. Suggested application: retain the character’s existing identity details, add the selected relationship paragraph, and use the matching directive and example below. The Ember guidance warns that excessive constraints can cause hesitation or repetition, so avoid turning the directive into a long prohibition list. [10]
4. Check that affection survives the boundary
Suggested setup check: review your configuration for contradictory wording. Keep descriptions of warmth, closeness, and permitted affection; remove instructions that invite sexual conversation. Then try an ordinary exchange about your day or a shared activity. Check two things separately: whether the desired affection remains, and whether sexual topics stay absent. One satisfactory exchange is not proof of reliable enforcement.
5. Correct drift without cancelling affection
Nomi’s February 2026 Q&A recommends immediately giving thumbs-down feedback that identifies the boundary violation, followed by a direct reminder in chat or an out-of-character message. This is troubleshooting guidance, not a guaranteed correction. For Kindroid, suggested troubleshooting is to clarify the existing Backstory or Response Directive rather than adding many overlapping rules. In either case, restate the permitted alternative—friendly or romantic affection without sexual conversation—instead of withdrawing all warmth. [4]
What this setup cannot guarantee
Nomi explicitly treats relationship types as starting points that can develop through interaction; Friend is not a permanent restriction. Its Boundaries documentation describes editable guidance, not a hard content filter. Kindroid’s moderation policy permits adult sexual roleplay, but that permission is not a user-selectable nonsexual setting. No independent boundary-adherence measurements were supplied for either provider. [1] [2] [11]
Plan and documentation limits
Nomi documents a free plan with 50 messages daily, but the reviewed Backstory+ and Boundaries articles do not specify field eligibility by tier. Do not assume a subscription strengthens enforcement. For Kindroid, the configuration guidance comes from an official search-index excerpt of the Ember LLM Guide; the live page did not fully render during the review. Relevant tier differences and a dedicated sexual-conversation lock could not be verified. Nomi’s documentation identifies the configuration fields but does not provide a complete screen-by-screen navigation path. [1] [3] [5] [10]
Keep this limitation in mind
Written boundaries and relationship settings are not a verified sexual-content lock. The reviewed documentation does not establish guaranteed enforcement for either provider. [0, 1, 9, 10]
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 Friend as the relationship type when creating a Nomi, using the creation-stage selection documented in the older setup guide. Current documentation describes Friend as a generally platonic, typically casual starting point—not a permanent platonic lock. The relationship can develop through conversation and shared context. 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: Friend 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 Friend selector or guarantee platonic behavior. Creation is free after registration, character counts depend on subscription, and Friend-specific entitlements are not specified.
Ourdream
Checked 2026-10-02
The supplied public-documentation audit supports concrete procedures for PNG/JSON character-card metadata import, message-memory pinning, and prompt-based non-English text-chat switching. It also describes relationship selection during character creation and reserves custom prompting beyond presets for Premium. It does not verify editable stored memory, dedicated pronoun controls, French/Japanese-specific support, or exact Friend/Romantic presets. No imports or chats were tested. Buyers should confirm these unresolved requirements and their plan access before subscribing.
- Editable or persistent memory
- Character-card or character import
- Documented multilingual text support
- Documented French chat setup
Why it matches: The creation page identifies Step 3 as the relationship-selection step, and the Boyfriend FAQ describes setting a relationship type during character creation that can take a platonic direction. This supports choosing a relationship direction during creation, but not an exact preset labeled Friend. A precise option-selection procedure, post-creation switching, feature-specific tier access, and enforcement of platonic behavior remain unverified.
Sources
Checked 2026-10-02
- How do Boundaries work? – Nomipedia – The Nomi AI Companion Wiki
- What is the difference between relationship types? – Nomipedia – The Nomi AI Companion Wiki
- What is Backstory+? – Nomipedia – The Nomi AI Companion Wiki
- 2026 02 Stream Summary – Nomipedia – The Nomi AI Companion Wiki
- Does Nomi offer refunds? – Nomipedia – The Nomi AI Companion Wiki
- Are there message character limits? – Nomipedia – The Nomi AI Companion Wiki
- How do I change my relationship status? – Replika
- Choosing a Subscription – Replika
- What is Replika Ultra? – Replika
- Ember LLM Guide · Kindroid Help Center
- Moderation Guidelines · Kindroid Help Center
- Characters | SpicyChat
- FAQs | SpicyChat
- 2025 July Q&A Summary – Nomipedia – The Nomi AI Companion Wiki
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.