Inkore · No access open

Your business. One fluid workspace.

Create, manage, measure and automate with tools connected by one continuous current.

Prepare my OBS sessionSee the system
Current state

This public site is live on inkore.io. No account, Wallet, or business tool is open.

Demonstration data
  1. 01CreateAI Rewrite
  2. 02EarnOffer Page
  3. 03BusinessLead Capture
  4. 04GrowthRevenue Link
  5. 05PlatformLead Notification

Everything flows. Nothing gets scattered.

Why Inkore

Fragmentation slows every step.

The same work crosses too many interfaces before producing a result anyone can read.

  1. Too many tools

    Every need adds another interface and another context.

  2. Too many subscriptions

    Costs accumulate before the chain becomes genuinely useful.

  3. Too much separated data

    Context fragments across silos that are difficult to review together.

  4. Too many manual tasks

    Information must be copied, checked, and reconciled.

  5. No shared view

    The action, the lead, and the outcome remain difficult to follow together.

Inkore targets a shared core where tools, data, and actions follow one continuous current.

Inkore Core

Five foundations, one context.

Every foundation has an explicit state. Local evidence is never presented as an open service.

  1. Identity

    The technical boundary exists, but no account, provider, or session is functional. The work is frozen by decision, with no restart date.

    Postponed · frozen

  2. Workspace

    The shared workspace waits for Organizations and demonstrated server isolation. The work is frozen by decision, with no restart date.

    Postponed · frozen by decision

  3. Wallet

    No credit, payment, purchase, or user balance is active. The work is frozen by decision, with no restart date.

    Postponed · frozen by decision

  4. Data

    The data foundation is accepted and locally proven within its scope, without a product schema.

    Foundation accepted locally

  5. Automation

    Business events, rules, and executions remain to be built after Core.

    Planned

Five verticals · One feature each

One current, five stations.

Each vertical begins with one focused, planned capability. None is available yet.

Filter by status

Showing 5 of 5 verticals.

  1. Create

    AI Rewrite

    Rewrite text with simple, controlled and measurable AI.

    Planned

  2. Earn

    Offer Page

    Publish a clear page to present an offer and guide visitors toward an action.

    Planned

  3. Business

    Lead Capture

    Capture and organize incoming prospect requests.

    Planned

  4. Growth

    Revenue Link

    Connect a campaign, a prospect and declared revenue.

    Planned

  5. Platform

    Lead Notification

    Trigger a notification when a new lead is received.

    Planned

Models under study, no final prices are set. See the pricing principles

Target journey — not started

Continuity to build from end to end.

This sequence describes the product vision. It is not operational yet.

Target journey — not started
  1. Rewrite an offer
  2. Publish a page
  3. Receive a lead
  4. Get notified
  5. Measure its origin

Product state

A public reading, without invented percentages.

The states below describe what is actually open to the public and what is not.

Status vocabularyAvailableFoundation accepted locallyPlannedPostponedNot authorized

  1. Public landing

    The French and English public site is deployed on inkore.io.

    Available

  2. PostgreSQL/Kysely foundation

    The data foundation is accepted and locally proven within its scope, without a product schema.

    Foundation accepted locally

  3. Identity

    Pure boundaries and a conditional architecture exist; no account or authentication runtime is open. The work is frozen by decision, with no restart date.

    Postponed · local foundation frozen

  4. Organizations

    An authorization model is written and tested deny-by-default, but no product consumes it. The work is frozen by decision, with no restart date.

    Postponed · frozen by decision

  5. Wallet

    Credits, product ledger, payment, and commercial balances are not implemented. The work is frozen by decision, with no restart date.

    Postponed · frozen by decision

  6. AI Rewrite

    The first Create feature is defined, but no prompt, provider, or AI processing is active.

    Planned

  7. Other verticals

    Offer Page, Lead Capture, Revenue Link, and Lead Notification remain unimplemented targets.

    Planned

Pricing

Models under consideration, no final prices.

No purchase is open and no commercial Wallet is available.

Free

Limited initial access is contemplated to discover value.

Pay as you go

A paid operation would show its cost before confirmation.

Subscription

A model reserved for regular usage that justifies it.

Commission

A commission may apply to selected future transactions, after validation.

Prices, credit ratios, taxes, margins, and refunds still require validation before any commercial opening.

  • No purchase is open.
  • No commercial Wallet is available.
  • The cost must be displayed before any paid operation.
  • Credits will not hide their monetary equivalent.

Security and trust

Separate evidence, ongoing work, and absences.

Guarantees remain limited to what the repository proves locally. They are neither an external audit nor production evidence.

Controls present

  • Landing without collection

    This page submits no form, creates no account, and processes no payment.

  • Explicit public states

    Planned features remain labelled as unavailable or planned.

  • Local data foundation

    This foundation has bounded local evidence for migrations; it creates no production guarantee.

Controls frozen by decision

  • Identity

    The conditional architecture and pure boundaries exist; no real account, session, or provider is open, and the work is frozen by decision, with no restart date.

  • Organizations

    Tenant isolation, server permissions, and atomic mutations are not operational; the work is frozen by decision, with no restart date.

  • Platform monitoring and infrastructure

    Production monitoring and infrastructure are neither selected nor implemented; they stay frozen with Platform Core.

Controls absent

  • Certifications

    No SOC 2 or ISO 27001 certification is claimed.

  • External audit

    No penetration test or external security audit is presented as successful.

  • Production guarantee

    No SLA or availability level is guaranteed.

FAQ

What to know before opening.

Short answers without invented dates, prices, or capabilities.

What is Inkore?

An ecosystem in construction that aims to connect creation, management, measurement, and automation in one workspace.

Is Inkore already available?

The public site is online, but no product is: no account, no Wallet, no business feature. Inkore Cue remains a local alpha, with no published release.

Why build only one feature per vertical?

To prove a focused, coherent journey before expanding each product family.

Will Inkore be free?

Free access is contemplated, with usage, subscription, or commission models where relevant. No price is validated.

How will data be protected?

Identity, Organizations, retention, and monitoring controls must be proved before opening. This landing collects no business data.

How is this different from a collection of SaaS tools?

Inkore targets a shared core and continuous journey instead of isolated products connected afterward.

How can I request access?

You can describe your needs by email from the Contact page. This does not reserve access to Cue or the platform.

Private access

Follow Inkore’s construction

The portfolio’s verified, dated progress is published on the Progress page; that is where you read what is shipped, in progress or frozen.

The Contact page opens your email application to write to Inkore. This site creates no account or product access.

See the progress
Private access — no opening scheduled