PynkBrain · part of Innovative AI Solutions

Pynk for you. Onyx for your business.

Pynk receives a request, classifies the intent, decides what matters, acts when allowed, notifies the right channel, and logs the receipt.

Live Pynkreceive · classify · decide · act · notify · log
starting demo...
classify
ReceiveWeb chat turn accepted
ClassifyPreference captured
DecideAfternoon calls should be avoided
Action blockMemory receipt prepared for the session
NotifyHandoff path ready when a business agent is needed
LogConversation state kept for the next turn
notify: channel ping ready
watching the intro — type anytime to take over

Two products, one substrate

Pynk feels personal. Onyx feels operational.

Same agent infrastructure, different jobs. Pynk keeps the human context close; Onyx turns inbound business moments into tracked work.

Personal agentPynk

Remembers your preferences, asks before sharing, and turns scattered life admin into clean next steps.

MemoryConsentTrusted handoffs
Business workforceOnyx

Handles customer intake, booking signals, follow-up, and operator-visible work for the business side.

LeadsSchedulingOperations

After signup

The demo now has a customer loop behind it.

The live chat can hand a new user into mission progress, adjustable autonomy, visible receipts, and daily return value.

01 · MissionA first-run checklist keeps setup moving.

Pynk tracks the activation steps behind the scenes so the first session can become a usable agent, not a dead-end chat.

02 · AutonomyYou decide how much she can do.

The agent can stay advisory, ask before action, or take approved work forward as trust grows.

03 · ReceiptsEvery useful action leaves a visible trail.

Saved preferences, active notes, and action receipts give the user a place to inspect what changed.

04 · BriefThe habit loop comes back to the user.

Daily brief preference is now part of the substrate, giving Pynk a retention path after signup.

Agent-to-agent coordination

The useful thing is the handoff. So we show the handoff.

Pynk is one node in a larger mesh. Personal context can stay private, while consented work moves to Onyx, the library, or a human operator with a visible receipt.

Open the live mesh →
contextskillhandoffnotifylogapproveYouPynkLibraryOnyxOperatorReceipt
  1. Sarah asks Pynk to plan dinner.
  2. Pynk checks Mike's allowed preferences.
  3. The restaurant's Onyx confirms availability.
  4. Sarah gets one decision, not another thread.

Library as product

The agent is only the visible edge. The library is what compounds.

Skills, playbooks, connectors, and operating doctrine turn one good demo into a reusable delivery system across PynkBrain, OnyxBrain, and GSDTechAI.

Reusable skillsCustomer playbooksAgent operating doctrineMCP connectorsWorkflow templatesCase-study proof

Deployment modes

Choose where the workforce runs.

Start with a hosted workforce, keep the agent inside your environment, or split coordination from tool execution.

Hosted agent workforce

We operate it
  • Fastest path to launch
  • Managed agent behavior
  • Receipts and operator follow-up

Customer-controlled

Runs in your environment
  • Your infra boundary
  • Your tool permissions
  • Your audit and retention rules

Hybrid

Shared control
  • Hosted coordination
  • Customer-side tools
  • Human handoff where needed

FAQ

Plain answers.

What is PynkBrain?

PynkBrain is the personal AI agent from Innovative AI Solutions: memory, coordination, and useful skills in one place.

Why show multiple agents?

The point is not another chat box. Pynk gets useful when it can coordinate with people, businesses, and shared skills.

How do deployments work?

Start hosted, run under your control, or split the work with a hybrid model. The right mode depends on the tools and data the agent needs to use.