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.
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.
YOUR AI · A NEW WORKING MODE
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.
AI proposes. People decide. Results are checked.
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.
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.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.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.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.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.
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.
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.

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.
Possible application directions, by selecting modules and agreeing the deployment scope.
Client context, proposal drafting, documents and organizing recurring processes.
A specialized knowledge base, source analysis, document drafts and continuity of expert work.
Project context, task handoff, content creation and keeping the team’s accumulated experience.
Code, websites, data, technical documentation and system integrations according to granted rights.
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.
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
Code, documents, data and projects remain in your tenant.
Separate infrastructure, access boundaries and governed keys.
Web, API, domains, files and developer access in one environment.
MetaCloud 1GB · L2, MetaCore OS foundation, Bridge and MCP connection.
Eight concrete workspace components. This is the base that works independently of which company process you later deploy.
Professional workspace capacity for persistent AI execution, not a temporary chat sandbox.
tenant.imone.ai surfaceAnother Codex tenant does not inherit access to this workspace.
A prepared structure for creation, testing, hosting, documents, execution data and the control interface.
MetaCloud 1GB · L2 stays active at least for the Codex entitlement period without a second KR charge.
Token access is limited to the tenant and does not become cluster / root authority.
codex:tenant scopeTechnical access is explicit and stays inside tenant bounds.
WordPress is available where granted; the exact web set depends on the tenant deployment.
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.
MCP URL, Client ID, OAuth PKCE and scope codex:tenant — enter them in your AI client.
After ordering, take the Token KEY in your account / packages panel. You can rotate it — the new KEY replaces the old one.
Paste public keys only (up to 8). They are applied to your tenant access in the panel — never paste a private key.
| Field | Value |
|---|---|
| MCP URL | https://metacore.lt/mcp/codex/sse |
| Client ID | c5e1004d-e3d1-42c8-8412-1acd80d99d1f |
| Client Secret | (empty) |
| Authorization URL | https://metacore.lt/mcp/codex/authorize |
| Token URL | https://metacore.lt/mcp/codex/token |
| Scope | codex:tenant |
| Auth method | PKCE only |
One isolated workspace has three practical paths: where work is kept, how access is granted and where the result is executed.
These capabilities exist on the platform, but their preparation depends on the ordered deployment scope and your tenant state.
Workshop and operator work are not automatically included in the base entitlement. Scope, terms and responsibilities are agreed before we start.
MetaCore specialists map the company, processes, systems and desired results, then design an individual operating architecture on the Codex entitlement.
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.
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 →The base tenant, the company operating layer, the workflow surface and deployment work are related, but not interchangeable. This section keeps those boundaries clear.
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.
Business Codex 50 remains the execution workspace after company deployment.
This belongs to the company deployment layer, and is not silently packed into the base tenant.
The workspace can support document, browser and API workflows where granted and authorized.
Operational controls and continuity remain part of the wider business system.
We are strengthening governance, verification and continuity of professional AI infrastructure. These directions extend the Codex 50 development vision.

Agent activity monitoring, data lineage, incidents and a shared event ledger.
AgentOps · Unified Event LedgerBaseline comparison, regression tests and quality criteria before a new version.
Technical EvalOpsModel selection by data category, quality need, price and response time.
Policy Model GatewayA client VPC or on-premises deployment model with control of credentials, external connections and updates.
Private DeploymentConnector packs with authentication, defined rights, audit and clear behavior during disruption.
Verified Connector PacksIdentity and access management, recovery drills and agreed recovery-time and data-loss objectives.
Enterprise IAM + DR · OIDC / SAML / SCIMBusiness Codex 50 · start
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.
The base plan and individual deployment work are presented separately, so the scope stays clear.