Galactre
USD

Choose how catalog prices and estimates appear. Checkout and account records remain in IDR.

Open Chat

GALACTRE / ECOSYSTEM

One model service.
A wider world to build.

Bring Galactre’s intelligence into a workflow with clear roles for identity, knowledge, development and operations. Explore how the Vinexel/Tyrant products fit together, and what is available today.

01 / FROM AN IDEA TO A WORKFLOW

Put each responsibility
in the right place.

Explore three application patterns. These are planning guides; selecting a pattern does not connect services or execute actions.

A focused answer, with a clear source.

Start with an authorized question and the context needed to answer it. GT provides the model response; your application decides which sources may be used and how the answer is reviewed.

Understand conversation context
  1. 01

    Your application

    Select the context

    Connect an authorized document or private text source in the conversation Workspace. Retrieval checks current permissions and records bounded source excerpts.

  2. 02

    GT

    Generate a proposed answer

    Send a focused task through the published browser interface. Review the response against the supplied evidence.

  3. 03

    Your application

    Present and verify

    Show source references, handle uncertainty and keep any real tools behind application permissions.

02 / PRODUCTS WITH DISTINCT ROLES

Understand the product.
Then verify the connection.

These are complementary products in the ecosystem, not a list of automatic integrations. The labels describe the published Galactre implementation, not live service health.

Identity and account access

IAM Central

Account flow implemented

Supports Galactre login and registration through a configured identity client. Permissions and callback configuration are verified by the server.

A shared identity does not share conversation history or grant administrator access.

Account access guide

Payment verification

Qrisbill

Credit billing flow implemented

Supports Galactre credit checkout, payment verification and owned invoice reconciliation. Availability depends on the configured payment environment.

Supports prepaid monthly and annual terms and paid top-ups. Renewals require a new invoice; automatic debit and autonomous agent wallets are not provided.

Credits and invoice guide

Developer assistant workspace

Vingolin

Native connector not published

A complementary place for conversations, code work and developer operations. Its workspace responsibilities remain separate from GT model responses.

No Galactre-specific workspace connector or automatic transfer of chats is published here.

Review connector availability

Documentation and knowledge

Avaread

Authorized document retrieval

Signed-in conversations can connect authorized documents through Workspace and retrieve bounded relevant excerpts. Access and document versions are checked again when used.

No automatic crawling, binary file extraction or cross-conversation memory. Source permissions do not follow a server API key.

Context and source guidance

Agent orchestration

Avaswarm

Native connector not published

A complementary direction for coordinated agent work. A working connector needs a released task contract, permission model, execution state and recovery behavior.

GT chat does not currently delegate or run a hosted multi-agent workflow.

Workflow responsibilities

Reusable capabilities and tools

Avaskill

Bounded read-only tools

Signed-in conversations can explicitly enable calculator and current-time tools. Validated tool execution and results are recorded before GT answers.

Instruction recipes remain prompts. Shell access, deployment, payments, arbitrary plugins and privileged actions are not enabled.

Browse instruction recipes

Application deployment and operations

Orisite

Native connector not published

A complementary hosting product for application operations. GT can help reason about supplied deployment context within a reviewed workflow.

No native deployment connector, server access or infrastructure action is exposed by GT chat.

Plan a reviewed release workflow

03 / SHARED PURPOSE, EXPLICIT ACCESS

Your data has
a product boundary.

Using the same ecosystem should make a workflow easier to understand. It does not mean every product may access everything.

Identity is the starting point

IAM Central establishes an account. Each product still checks resource ownership, membership and the permission required for the operation.

Context must be deliberately supplied

Galactre works with your submitted text and bounded owned conversation context. It does not automatically retrieve documents, inspect repositories or search another product’s history.

Actions need their own authority

A response can propose a next step. Tool execution, infrastructure changes and payment approval remain with the application and its explicit permissions.

04 / BEFORE YOU CONNECT

A useful integration
needs more than a link.

Use these checks when evaluating a connector or planning an application workflow.

A published contract

Identify the supported endpoint or connector, its version and the operations it actually exposes.

Explicit access

Specify the identity, owner, permission scopes and context that may cross each product boundary.

Operational evidence

Verify success, failure and recovery with the deployed services. A diagram does not establish a working connection.

Ongoing ownership

Name who maintains credentials, handles incidents and manages data deletion, payment review and compatibility.

05 / ECOSYSTEM QUESTIONS

Know what connects.
Know what it means.

How should integrations select a GT version?

Use a family ID for its promoted default or an exact release ID for a controlled integration. Record the resolved model_id and release_hash with the result. Revalidate prompts, task constraints and evaluation evidence before adopting another release; model versioning does not grant access to another product.

What is Galactre’s role in the ecosystem?

Galactre develops GT, its AI model family, and operates the conversation experience and developer services. GT produces text responses; Galactre manages model access, conversation context and integration guidance. Other products have their own responsibilities for workspaces, knowledge, orchestration, identity, billing or deployment.

Are all products already connected?

No. The directory distinguishes implemented account and billing flows from native connectors that are not published. Runtime health, credentials, access and deployment must also be checked before use.

Does signing in connect all my product data?

No. A shared identity does not merge conversations, documents, tools or permissions. Each application must authorize access to its own resources.

Can I use Galactre with my own application?

Start with the developer contract. Browser integrations use same-origin sessions and CSRF. Backend applications use expiring, model-scoped server keys from API Access with POST /api/v1/responses and an Idempotency-Key. Request status, streaming and cancellation follow the documented Galactre contract.

Is this a partner marketplace or certification program?

No. This page explains product roles in the Vinexel/Tyrant ecosystem. It does not certify third parties, offer installable connector listings or claim a public partner membership program.

Do the workflow examples run tools or create payments?

No. The examples explain responsibilities. Selecting a workflow does not send a prompt, connect an account, execute a tool, deploy an application or create a payment.

BUILD FROM A CLEAR FOUNDATION

Start with Galactre.
Connect with purpose.