A company team and a MetaCore AI Persona planning a project together — conceptual illustration
BUSINESS CODEX 50 · PROFESSIONAL AI WORKSPACE

Business Codex 50.Your governed AI laboratory.

A 50 GB Codex workspace with DirectAdmin and developer access. A MetaCloud 1GB space and the MetaCore OS foundation are activated with it: for your projects, files and work continuity. AI team roles, the knowledge core and integrations are prepared according to the chosen deployment scope.

50 GB · Isolated workspaceMetaCloud 1GB · L2 · Work continuityBridge · MCP · SSH by granted rights
Human + AI · Conceptual illustration

YOUR AI · A NEW WORKING MODE

Your model becomes a more capable AI collaborator.

Keep your model. Give it a clear, checkable way to work.

MetaCore does not change the model's weights. It adds work context, an AI Persona role, expert methods and boundaries set by the human. Beyond one-off answers, your AI can guide a task more consistently, suggest the next step and show work you can check.

  • Attentive dialogue
  • A distinct Persona voice
  • Expert guidance
  • Approved action

AI proposes. People decide. Results are checked.

OS BoostMetaCloud 1GBBusiness Codex 50Enterprise
Compare packages →
One person · one governed infrastructure

Your AI laboratory, where work continues.

Codex 50 connects a professional server workspace, personal context and access to AI tools. You govern the tenant and access rights; the AI Persona works only within the scope granted to it.

01 · Included in Codex 50

50 GB server space

A dedicated Codex tenant with DirectAdmin, file, domain, web and developer access. Projects, documents, code and work results stay in the tenant space.

Access through DirectAdmin and SSH according to granted rights.
02 · Included without a second KR charge

MetaCloud 1GB + OS

A private MetaCloud space holds session state, files, handoffs and work history. MetaCore OS provides a shared methodological foundation; it is not copied into every tenant.

The MetaCloud entitlement stays active at least for the Codex entitlement period.
03 · Prepared according to need

AI Team and knowledge CORE

Selected documents are arranged, indexed and linked to projects according to the agreed deployment; AI team roles and an individual AI Persona are prepared.

Knowledge ingest and Persona configuration are not an automatic base.
04 · Human control

Your control path

Through panel.metacore.lt you see the account, plans and your spaces. Server and developer tools run through separate tenant accesses; backup and restore procedure is selected according to the deployment.

Decisions and permissions stay in human hands.
AI laboratory diagram: a person governs the Codex 50 tenant, MetaCloud provides continuity, the AI team is connected according to the deployment, results are saved.
Architecture diagram · AI Persona and AI Team configuration depend on the agreed deployment scope.
From conversation to a saved result

Through a compatible MCP client or granted Bridge access you discuss the task with the AI Persona. It can propose a plan, use granted tools and, if configured that way, hand part of the work to the AI team. Results, decisions and handoffs are saved in authorized workspaces.

Review the technical base →

One platform, different activities: companies and teams, learning and LAB, creation, family or personal projects, real-estate objects. Structure and access for each area are set separately; individual systems, model preparation and integrations depend on the deployment scope.

BUSINESS CODEX 50 · FOR PROFESSIONAL AI EXECUTION

A professional AI space.
Built for your activity to grow.

More order in knowledge, clarity in processes and continuity in projects. Business Codex 50 is a professional AI work foundation that can be adapted to different activities, teams and specializations.

Holographic Codex work-infrastructure tower with a glowing M mark
Conceptual infrastructure illustration
CONTEXT · SPECIALIZATION · EXECUTION

Business Codex 50

Your documents, knowledge and projects — in an isolated 50 GB workspace. According to the chosen deployment scope, expert modules, AI roles and integrations form a work system fitted to a specific activity.

50 GB
For knowledge, documents, code and projects
MetaCloud 1GB · L2
For files, context and work continuity
Bridge · MCP · SSH
Access according to granted rights
Domain · DirectAdmin
For a separately governed work environment
5 200 KR/ mo.or €520 / mo. via a separate EUR billing path
Order Business Codex 50 →
ADAPTABLE TO YOUR ACTIVITY

One foundation. Different specializations.

Possible application directions, by selecting modules and agreeing the deployment scope.

01 · BUSINESS AND SERVICES

Clearer daily work

Client context, proposal drafting, documents and organizing recurring processes.

02 · PROFESSIONAL PRACTICE

Knowledge you can work with

A specialized knowledge base, source analysis, document drafts and continuity of expert work.

03 · TEAMS AND CREATION

From idea to a shared result

Project context, task handoff, content creation and keeping the team’s accumulated experience.

04 · TECHNOLOGY AND ENGINEERING

Solutions you implement

Code, websites, data, technical documentation and system integrations according to granted rights.

INCLUDED WITH CODEX 50 · OR SEPARATELY

MetaCloud 1GB

A private space for files and work continuity. With an active Codex 50 it is granted together without a second KR charge; it is also available separately for personal work.

FOR LARGER TECHNICAL SCOPE

Enterprise Quantum 150GB

A larger execution space, activated on request and an agreed project scope.

Workspace and deployment are separate. Codex 50 provides the execution infrastructure. Individual company systems, expert AI roles, training and integrations are agreed according to the deployment scope.

Professional execution workspace

Business Codex 50 — a clear base for real AI work.

An isolated work environment where your team can create, execute and save AI work results. The base entitlement is defined in advance; company systems and individual integrations are designed separately.

TECHNICAL SUMMARY · 50 GB persistent space · isolated tenant · MetaCloud 1GB · L2 · Bridge / MCP / SSH
A MetaCore AI Persona helps one company team coordinate production, warehouse, transport and a secure data workspace; people make the decisions.
BUSINESS DEPLOYMENT EXAMPLE · CONCEPTUAL ILLUSTRATIONAn AI Persona can help coordinate company processes; the concrete system is designed separately.
  • AI Persona
  • Team
  • Production
  • Warehouse
  • Logistics
  • Data
01

50 GB workspace

Code, documents, data and projects remain in your tenant.

02

Isolated tenant

Separate infrastructure, access boundaries and governed keys.

03

Execution surface

Web, API, domains, files and developer access in one environment.

04

Context continuity

MetaCloud 1GB · L2, MetaCore OS foundation, Bridge and MCP connection.

INCLUDED

Base entitlement — what every client receives

Eight concrete workspace components. This is the base that works independently of which company process you later deploy.

1. 50 GB persistent workspace

  • Persistent tenant storage
  • Code and projects
  • Documents and artifacts
  • Data and indexes

Professional workspace capacity for persistent AI execution, not a temporary chat sandbox.

2. Isolated tenant infrastructure

  • Dedicated Codex tenant
  • DirectAdmin tenant
  • tenant.imone.ai surface
  • Neighbor isolation

Another Codex tenant does not inherit access to this workspace.

CODEX Virtual Server · open Cloud

3. Standard workspace zones

playground/domains/docs/data/dashboard/

A prepared structure for creation, testing, hosting, documents, execution data and the control interface.

4. MetaCloud 1GB · L2 included

  • Memory / context indexes
  • Coordination
  • Handoff continuity
  • MetaCore OS foundation

MetaCloud 1GB · L2 stays active at least for the Codex entitlement period without a second KR charge.

5. Bridge + tenant authorization

  • MetaCore Bridge
  • MCTemp tenant key
  • Replaceable entitlement
  • AI access limited to the tenant

Token access is limited to the tenant and does not become cluster / root authority.

6. Codex MCP access

  • Codex MCP endpoint
  • OAuth PKCE
  • codex:tenant scope
  • Compatible MCP clients
CursorClaude DesktopGrokFuture compatible clients

7. Developer access

  • SSH public-key management
  • Up to 8 public keys
  • Direct tenant shell access
  • Tenant sandbox isolation

Technical access is explicit and stays inside tenant bounds.

8. Web and execution environment

  • Website / domain capability
  • Web application hosting
  • PHP / static / code execution
  • API endpoints
  • Artifacts / deployment

WordPress is available where granted; the exact web set depends on the tenant deployment.

Business Codex 50 · MCP · Token · SSH

What you get for connection: MCP doors, Token panel and SSH.

After ordering the Codex 50 package, your panel shows your Token KEY with rotation and lets you paste public SSH keys onto your Codex server. Below are the public MCP connection doors for AI clients (Cursor, Claude, etc.). Your personal Token KEY is not in the table.

01 · MCP doors

Public connection fields

MCP URL, Client ID, OAuth PKCE and scope codex:tenant — enter them in your AI client.

02 · Token panel

KEY with rotation

After ordering, take the Token KEY in your account / packages panel. You can rotate it — the new KEY replaces the old one.

03 · SSH access

Public keys to the server

Paste public keys only (up to 8). They are applied to your tenant access in the panel — never paste a private key.

Business Codex 50 · MCP doors
FieldValue
MCP URLhttps://metacore.lt/mcp/codex/sse
Client IDc5e1004d-e3d1-42c8-8412-1acd80d99d1f
Client Secret(empty)
Authorization URLhttps://metacore.lt/mcp/codex/authorize
Token URLhttps://metacore.lt/mcp/codex/token
Scopecodex:tenant
Auth methodPKCE only
Where is the Token KEY? Order Codex 50 → Activate / packages panel. Rotation is there when you need to replace the key. The token stays within tenant scope (codex:tenant).
TECHNICAL OPERATION

How the Codex 50 parts connect

One isolated workspace has three practical paths: where work is kept, how access is granted and where the result is executed.

01 · Files and work zones

docs/ is for documents, data/ for execution data, playground/ for creation and trials. Code, projects and artifacts are stored in the persistent 50 GB tenant space.

Work content stays inside tenant bounds.

02 · Access by rights

A developer can connect over SSH with a public key (up to 8 keys). A compatible MCP client connects via OAuth PKCE with the codex:tenant scope; Bridge uses the tenant MCTemp key.

A tenant right is not a cluster or root right.

03 · Execution and continuity

domains/ and dashboard/ zones help present web and control surfaces. PHP, static content, API and artifact deployment depend on the granted tenant set; MetaCloud 1GB · L2 supports file, context and handoff continuity.

WordPress and individual integrations are agreed separately.
ATTACHABLE

Capabilities according to your need

These capabilities exist on the platform, but their preparation depends on the ordered deployment scope and your tenant state.

AI team workspace template

agents/handoffs/indexes/knowledge/projects/

A shared AI team operating template exists, but it does not guarantee an identical pre-built structure in every base tenant.

Company knowledge ingest

Archive preservation → extraction → classification → indexing → sensitivity marking → a searchable company corpus.

A deployment / onboarding capability, not an automatic monthly result.

WordPress / product grant

Web product surfaces and WordPress may be granted where tenant state and the ordered deployment support them.

A conditional capability.
CUSTOM

Business deployment: from a process to a working system

Workshop and operator work are not automatically included in the base entitlement. Scope, terms and responsibilities are agreed before we start.

What this means

MetaCore specialists map the company, processes, systems and desired results, then design an individual operating architecture on the Codex entitlement.

Examples

CRMFinanceProcurementInventoryIndividual websiteKnowledge ingestIndividual workflowsEndpoint integration

Not included in the 5200 KR base

Individual CRM/finance/procurement builds · guaranteed mass indexing/OCR of a legacy archive · consulting/operator hours · individual SLA/support allocation · model inference credits · arbitrary individual domains · commissioned business architecture.

Reference architecture exampleAutoAR shows what can be built on Business Codex 50. Its CRM, finance, procurement, website and company knowledge system are results of individual deployment — not automatic contents of the base package.

What 5200 KR pays for

50 GB persistent workspaceIsolated tenantDirectAdminMetaCloud 1GB · L2MetaCore OS foundationBridgeMCPMCTempSSHExecution surfaceContinuityTenant isolation

Base-package boundary

AI-provider subscriptions / inference · individual company systems · operator / consultant hours · commissioned architecture · guaranteed OCR or semantic ingest of legacy archives · individual SLA · root / operator cluster rights · unlimited storage / compute · arbitrary execution of external systems.

Have a process you want to strengthen? We start from its boundaries, data and a measurable result.

Discuss business deployment →
Business Codex 50 · scope boundaries

Know what is included in the workspace — and what belongs to deployment.

The base tenant, the company operating layer, the workflow surface and deployment work are related, but not interchangeable. This section keeps those boundaries clear.

How does the full solution come together?

Codex 50 provides the technical workspace. Organization context, AI Persona, expert roles and concrete workflows are prepared on this base according to the agreed deployment scope.

This separation makes it clear which infrastructure is included in the plan and which solutions are built for a specific person, team or organization.

WORKSPACE / BASE

Technical work environment

Business Codex 50 remains the execution workspace after company deployment.

Dedicated 50 GB tenant environmentDomains, web and file workspace
COMPANY LAYER / DEPLOYMENT

Organization context and roles

This belongs to the company deployment layer, and is not silently packed into the base tenant.

Company MetaCore OS and contextCompany AI Persona and expert roles
WORKFLOW SURFACE

Tools around real business work

The workspace can support document, browser and API workflows where granted and authorized.

Browser, documents, PDF and API workflows
CONTROL / CONTINUITY

Execution must stay governed

Operational controls and continuity remain part of the wider business system.

Bounded execution, audit, copies and continuity
Clear scope: the base Business Codex 50 entitlement is defined in the technical-scope section above. AI Persona, expert configuration and organization-fitted systems are prepared according to the chosen deployment scope.
DEVELOPMENT DIRECTIONS · ROADMAP / LAB

A firm foundation today.
More capability tomorrow.

We are strengthening governance, verification and continuity of professional AI infrastructure. These directions extend the Codex 50 development vision.

Six Codex 50 development directions, joined into a governed AI infrastructure path
Governed evolutionMonitoring → verification → model selection → private infrastructure → integrations → recovery
01
MONITORING

A clear action history

Agent activity monitoring, data lineage, incidents and a shared event ledger.

AgentOps · Unified Event Ledger
02
QUALITY

Verification before an update

Baseline comparison, regression tests and quality criteria before a new version.

Technical EvalOps
03
MODEL SELECTION

The right model for the task

Model selection by data category, quality need, price and response time.

Policy Model Gateway
04
PRIVATE INFRASTRUCTURE

Deployment in your environment

A client VPC or on-premises deployment model with control of credentials, external connections and updates.

Private Deployment
05
INTEGRATIONS

Verified system connections

Connector packs with authentication, defined rights, audit and clear behavior during disruption.

Verified Connector Packs
06
ACCESS AND RECOVERY

Readiness to continue work

Identity and access management, recovery drills and agreed recovery-time and data-loss objectives.

Enterprise IAM + DR · OIDC / SAML / SCIM
DEVELOPMENT STATUS

These capabilities are planned or partly verified in LAB. They are not Codex 50 features available to every client. Availability is confirmed only after the relevant verification and an agreed concrete deployment scope.

Business Codex 50 · start

Your AI laboratory can start from one governed space.

Get an isolated 50 GB Codex workspace, DirectAdmin access, MetaCloud 1GB and the MetaCore OS foundation. We prepare the AI Persona, expert roles, knowledge CORE and integrations according to the deployment scope you choose.

  • 50 GB tenant space
  • MetaCloud 1GB
  • DirectAdmin and SSH
  • panel.metacore.lt control
Order Codex 50 → Discuss business deployment

The base plan and individual deployment work are presented separately, so the scope stays clear.