The self-serve product answers a question. Enterprise builds a machine around your pipeline — with a human consultant who owns the output, an approval committee that governs it, and connectors that ground every analysis in your own data.
Enterprise is not a bigger plan. It is a different shape of engagement — the platform, plus the people and the plumbing that make it fit one organization's actual work.
Not a support queue. A person who scopes the engagement, turns your decision criteria into the system's logic, reads every deliverable before it leaves, and sends it back when it isn't right.
In the engagement described below, the consultant rejected several drafts of a portfolio deliverable before it shipped — including one that compared each asset's price against a number derived from that same price. The AI would have published it. The human wouldn't.
A standing panel of independent frontier models on separate clouds reviews the decisions that matter: methodology changes, what ships, what gets published, and what gets held back.
Your edge is your data. Enterprise wraps your sources — market and listing platforms, loan servicing and core banking, e-discovery and document repositories, ERP and logistics, claims and policy systems, GIS and permits, or simply your own warehouse — so the debate reasons over your live pipeline and cites it, not just the open web.
Enterprise reads what a team can't. Not sampled, not keyword-filtered — read, cross-referenced, and reasoned over, with contradictions and gaps reported rather than smoothed away.
Managed by us, inside your cloud account with your own keys, installed on-premises behind your own firewall, or sealed and air-gapped with no outbound connectivity at all.
For organizations with compliance obligations, on-premises matters more than any certificate we could hold — your data never leaves the envelope you already had audited. See the four tiers below.
The model roster is configuration, not doctrine. Exclude any vendor, cloud or jurisdiction — competitive, legal, contractual or policy reasons, no justification required. Restrict to open-weight models you host yourself. Or pin the approved list your risk committee already blessed.
The method survives the constraint. Panels get composed from whatever roster you permit and the debate works the same, because the process is the product, not any particular model.
Every Enterprise engagement follows the same five steps. The first four are usually measured in days, not quarters.
What decisions do you actually need supported, what data feeds them, and what does a defensible answer have to contain for your investment committee, your board, or your regulator? This is a conversation, not a questionnaire.
Your buy-box, thresholds, disqualifiers and house rules get written into the system as explicit, inspectable logic — not a prompt. You can read it, argue with it, and change it. In the engagement below, the client's own rules ("institutional sellers only," "must be transactable remotely") became lines in a thesis file that every candidate is scored against.
We build against your APIs in an isolated environment, run real cases end to end, and review the output with you before anything touches production. Security gates are cleared before a single credential of yours is stored.
Analysis runs at whatever scale the question needs — a single decision, a portfolio, a continuous scan. Your consultant reviews the deliverable; the Executive Committee reviews anything consequential; then it goes to you in the format you'll actually use.
Most engagements don't end at delivery. They become standing capability — a scan that runs every few hours, a weekly ranked list, a pipeline that gets smarter as your criteria sharpen.
Data isolation is both a security requirement and a design choice. Pick the tier your obligations demand — the analysis is the same; the boundary moves.
We run it. Your account gets isolated storage and its own connectors; your data is never co-mingled with another client's, retained only long enough to deliver, and never used to train anything.
The system runs inside your own cloud account against your own model credentials. We operate it; you own the infrastructure, the logs and the bill. The common choice for most enterprises.
Installed entirely inside your own network. Nothing crosses your perimeter, and your existing certified environment is the control boundary — the honest answer to most compliance questions we're asked.
Air-gap-capable, running open-weight models you control, grounded only on your own corpus. Built for classified, defense and sovereign contexts where no egress is permitted at all.
3Dogs Nexus is not SOC 2, ISO 27001, FedRAMP, CMMC or HIPAA certified, and we are not going to imply otherwise on a marketing page. If a certificate is a hard procurement gate for you, say so on the first call and we will tell you honestly whether we can clear it. Here is how the requirement actually gets met today:
Every engagement is scoped individually. Price moves with the data sources connected, the decision types supported, the deployment tier, and the volume of analysis you run. Custom work — a bespoke connector, a portfolio underwrite, a document investigation — is quoted as part of that scope, not billed by surprise.
Solo, Professional and Business plans are self-serve and priced publicly. Enterprise is the tier where a person, a committee and your own data enter the picture.
Three published examples of Enterprise-scale work. The first is a live client engagement, anonymized; the other two are documented capability tests you can check line by line.
Four projects for one buyer: loan-tape underwriting, a nationwide always-on search, a valuation wave of up to eighty properties, and a deep portfolio underwrite. 8,304 metered model calls, 93 debate panels, 1,312 analyst seats.
Eight planted red flags in a simulated acquisition. Eight found — plus an honest report that the room was substantively empty when it was.
The real Enron corpus, no instruction on what to look for. Named the vehicles, found the suppressed internal dissent, and flagged its own evidentiary gap.
Twenty minutes is usually enough to tell whether Enterprise fits what you're trying to do. If it doesn't, we'll say so.