Features

A public feature map aligned with the real INKORA application.

This page separates live product capabilities from in-development route scaffolds and future studio modules.

Available now

Core workflow features already exist in the current build.

The project foundation is real: authentication, portal routing, studio access, tattoo requests, project continuity, and artist review.

Available nowAuth

Authentication foundation

Secure account access and a workspace shaped around how you use INKORA.

Available nowClient

Client request intake

Tattoo requests and request-linked client flow are already supported.

Available nowArtist

Artist review workflow

Artists can review incoming work and operate from project-aware surfaces.

Available nowSecurity

Studio permissions

Memberships, tenant boundaries, and role checks remain part of the existing backend architecture.

In development

Portal architecture is broader than the currently completed workflows.

Owner, manager, and reception experiences already have structured route trees. The core task now is finishing those product surfaces without overselling unfinished areas.

In Development

Client portal

Tattoo requests, projects, and profile continuity are the strongest current areas.

In Development

Artist portal

Review queue and project continuity are live. Surrounding operations pages are still being built out.

In Development

Studio leadership portals

Owner, manager, and reception routes exist with real navigation but many modules remain clearly marked for later work.

For clients

Clients move from inquiry to project visibility without losing the thread.

INKORA is designed so clients no longer need to rebuild context every time they return to the studio.

  • One structured tattoo request flow
  • Project-linked references and clarifications
  • Protected return access through the client portal
  • Expansion path for later documents and aftercare
Read the client experience
Available nowPortal preview

Client product preview

Placeholder for screenshots from the current request, profile, and project surfaces.

For studios

Studios get a structure for operations without pretending every module is already done.

The product architecture supports expansion into broader studio operations, but only the released and in-progress areas are described as active.

  • Role-aware public entry into the application
  • Project-centered studio workflow
  • Protected membership-aware access
  • Future-ready foundation for operations modules
See studio management
In DevelopmentPortal preview

Studio operations preview

Placeholder for future captures from owner, manager, and reception pages.

Next exploration paths

Explore the feature areas most relevant to your role.

Each feature route reflects the actual state of the application and keeps planned work visibly separated.

Access the product

Use the public site to understand the scope, then enter the real application through the existing auth flow.

Create an account to get started, or sign in if you already have one.