Development Tools Branding

Aligning external tools with the NeuAIs platform identity.

Context

The platform relies on self-hosted development tools rather than external services. Two tools—GitArena (Git platform) and Lapdev (web IDE)—have been integrated into the codebase and rebranded to match the NeuAIs identity.

This document describes the branding approach and integration pattern.

Brand Requirements

From the established brand guidelines (mgmt/brand/BRAND_QUICK.md):

• Name: NeuAIs (strict spelling)
• Colors: Black (#000000), White (#FFFFFF), Greys (#1a1a1a, #666666, #cccccc)
• No gradients
• No emojis
• Dark theme default
• Direct, minimal, technical tone

Tools Overview

NeuAIs Git (GitArena)

Location: neuais.com/tools/git/gitarena/
Language: Rust (Axum web framework)
Port: 3000

Self-hosted Git platform with repository management, issue tracking, and code review.

Branding Applied:

• Logo replaced with NeuAIs mark (black lightning bolt)
• Site title: “NeuAIs Git”
• Custom CSS (neuais-brand.css) enforcing black/white/grey palette
• Dark theme default
• Navigation updated

NeuAIs IDE (Lapdev)

Location: neuais.com/tools/ide/lapdev-lapdev-cli/
Language: Rust (Leptos UI)
Port: 3001

Full web-based IDE with terminal, LSP, extensions, and Kubernetes integration.

Branding Applied:

• README rebranded
• Configuration defaults updated
• Instance name: “NeuAIs IDE”

Integration with Manifest

Both tools are defined in the manifest CSV as tool type entries:

type,name,description,template,language,port
tool,git,NeuAIs Git server,gitarena,rust,3000
tool,ide,NeuAIs IDE server,lapdev,rust,3001

When the manifest is processed, a generator (automation/generators/generate-tools.js) produces configuration files:

• generated/tools/git/config.env - GitArena configuration
• generated/tools/ide/config.env - Lapdev configuration

These configs follow the same environment-driven pattern as all platform services.

Deployment

Both tools use the platform’s standard deployment pattern:

Build:

# GitArena
cd tools/git/gitarena
cargo build --release

# Lapdev
cd tools/ide/lapdev-lapdev-cli
cargo build --release -p lapdev-ws

Run:

# From automation directory
./run-gitarena.sh   # Port 3000
./run-lapdev.sh     # Port 3001

Run scripts load generated configs and start services with correct environment variables.

Configuration Pattern

Generated configs include:

# NeuAIs Git
BIND_ADDRESS=0.0.0.0:3000
DATABASE_URL=postgresql://localhost/neuais
INSTANCE_NAME=NeuAIs Git
THEME=dark

# NeuAIs IDE
LAPDEV_WS_PORT=3001
LAPDEV_HOST=0.0.0.0
DATABASE_URL=postgresql://localhost/neuais
LAPDEV_INSTANCE_NAME=NeuAIs IDE
LAPDEV_THEME=dark

Same pattern as services and agents: environment variables, predictable ports, Postgres dependency.

Branding Assets

Logo: neuais.com/public-shared/assets/svgs/brand/logo-black.svg

Three variants created for GitArena:

• logo.svg - Base logo
• logo_text.svg - Logo + “NeuAIs” text
• logo_border.svg - Logo in bordered box

CSS variables enforce color palette:

:root {
  --neuais-black: #000000;
  --neuais-dark-grey: #1a1a1a;
  --neuais-grey: #666666;
  --neuais-light-grey: #cccccc;
  --neuais-white: #FFFFFF;
}

Summary

Development tools follow the same integration pattern as platform services:

• Defined in manifest
• Configuration generated automatically
• Standard deployment pattern
• Consistent branding
• Environment-driven config

This ensures tools behave like first-class platform components rather than external add-ons.

Location: docs-internal/integration/
Related: Agent integration patterns (smo-ric-agent-integration.md)