One identity. Clear access.
Use one Core account across registered apps. Give each person the roles they need, with permissions checked against their current access.
Identity & authorizationTHE NCE CORE PLATFORM
Bring your people, applications, data, and workflows together. One shared foundation, with your organization in control.
Public platform overview. Private, authenticated workspace.
01 / THE PLATFORM
NCE Core is the common layer behind your applications. Manage who can access what, connect shared services, and give every app a foundation to build on.
Use one Core account across registered apps. Give each person the roles they need, with permissions checked against their current access.
Identity & authorizationConnect datasets, transformations, and events. Share information across approved deployments while preserving its permissions and source.
Core Data & Data FabricCompose pipelines, rule-based agents, and workflows. Follow execution traces and keep both people and agent actions within their granted access.
Core Agents & WorkflowsOrganize applications through a shared marketplace. Connect existing apps or develop new ones with Core identity, services, and organization context.
Marketplace & App Factory02 / INTEGRATIONS
Bring your existing tools into the picture. Core connects through shared contracts and authenticated APIs, so applications can work together wherever they run.
Explore connection optionsEvery connection is intentional.
Administrators approve application access and scope connections to the right environment.
Broker sign-in from compatible OpenID Connect providers, including Keycloak, Microsoft Entra ID, Google, and Amazon Cognito.
OPENID CONNECT / OAUTH 2.0Publish integration contracts, manage environment-specific settings, and explicitly approve which applications can use them.
AUTHENTICATED HTTPS APISConnect independently hosted applications or Core-managed apps to shared identity, permissions, and services.
SERVICE-BOUND ACCESSKeep applications on their own infrastructure, or connect an existing Kubernetes namespace for approved workload deployment.
EXTERNAL HOSTING / KUBERNETESA shared platform where it helps. Application-level control where you need it.
Administrators manage a shared platform connection. Each application needs explicit approval to inherit it, and access is checked on every authorized operation.
03 / FROM CONNECTION TO COORDINATION
Start with the applications and people you have. Add shared services as your organization needs them.
Set up your organization, invite people, and assign roles. Each application gets its own registered identity and permission vocabulary.
Register applications, approve integrations, and select the right environment. Share a platform connection or configure one for a particular app.
Use Core data, workflows, chat, and search across your connected tools. Keep permissions and organization context attached along the way.
OPEN TO EXPLORE. CONTROLLED TO USE.
Explore what NCE Core does here. When it is time to work, enter Core through its secure sign-in. Your organization determines which applications, data, and actions you can access.
Sign in to NCE CoreAccess is invitation-only. Need an account? Contact your organization administrator.
Authenticated accounts
Organization-specific access
Current roles & permissions
Environment boundaries
A FEW MORE DETAILS
NCE Core is an organization control plane: a common foundation for identity, authorization, applications, data, and workflows. It provides shared services that integrated applications use through authenticated APIs, with organization and environment context attached.
Yes. This website explains the platform and is publicly accessible. The Core workspace at core.nnytech.ai requires sign-in. Account creation is invitation-only, and signing in gives you the access your organization has explicitly granted.
No. Applications can run on their own infrastructure and connect to Core through registered identities and authenticated HTTPS APIs. Core can also manage approved application workloads through an existing Kubernetes namespace.
An administrator publishes a contract, configures a connection for an environment, and approves application consumption. Roles and policy determine who may use it. Publishing an integration does not automatically grant access or subscribe to a service.
Core AI currently provides permission-aware search and cited retrieval across application datasets. Core Agents use bounded, deterministic rules, and Core Training supports simulation and evaluation. Model generation is not enabled by default; an integration listing does not mean a paid model is connected.