mirror of
https://github.com/hanzo-apps/hanzo.ai.git
synced 2026-10-30 14:58:08 +00:00
zeekay
8b354c25ad
Savings (components/sales/Savings, lib/savings): the tokens a team uses a month, by model or by spend, at the providers' list rates, on Hanzo Cloud moved to an Enso SKU plus the members on Team, and on the reader's own GPUs on all month. Every rate is read when the page opens: the price list (GET /v1/pricing, its on-demand GPU hour too), the plan list (Team's member month) and the model list (what Hanzo bills a provider's model). The volumes, people and GPUs are the reader's, and the page says it opens with an example. Each figure says what it assumes; the GPU figure leaves the agreement out and says so, with where it meets list and that sizing is done with the customer. /calculator carries the same calculator. Your own GPUs: Zen 6's prefill as Hanzo measured it on one DGX Spark (lib/data/zen6-spark.json, scripts/zen6.py, from the enterprise-story branch) and what a Zen 6 Max rack is made of, from NVIDIA's pages (Rack, with Zen 6 Max's page). That branch's Cloud against Enterprise board is left off /benchmarks: it prints a 96.0% the page's gate refuses. Proof shows six of the data room's case studies. Partners are the programmes that exist: affiliates, White-label and the agency's plans as the plan list sells them, and the clouds Hanzo deploys on, captioned as vendors, not partners. No company is called a partner: none is on record.
51 lines
2.2 KiB
TypeScript
51 lines
2.2 KiB
TypeScript
'use client'
|
|
|
|
import { Box, XStack, YStack } from '@hanzo/ui'
|
|
import { Grid } from '@hanzo/ui/grid'
|
|
import { Action, Display, Leaf, Lede, Line } from '@hanzo/ui/marketing'
|
|
import { Band, Head } from '@/components/marketing/band'
|
|
import Rack from '@/components/enterprise/Rack'
|
|
|
|
const POINTS = [
|
|
['One name', 'You call Zen 6 Max. You never choose among the models behind it.'],
|
|
['The right specialist, per request', 'Enso reads each request and runs it on the specialist built for that kind of work, transparently.'],
|
|
['Long context', 'A long context, for large codebases and long documents.'],
|
|
['Tools and code', 'Tool calls and code, built in.'],
|
|
] as const
|
|
|
|
export default function MaxView() {
|
|
return (
|
|
<Box minH="100vh" $platform-web={{ color: 'var(--foreground)' }}>
|
|
<Band rule={false} pad="$14" measure={1000}>
|
|
<YStack gap={24} items="center" $platform-web={{ textAlign: 'center' }}>
|
|
<Display render="h1" fontSize="3rem" $lg={{ fontSize: '5rem' }}>Zen 6 Max</Display>
|
|
<Lede maxW={720}>
|
|
3.7 trillion parameters across a routed fusion. Each request runs on the specialist Enso picks, so it behaves as one
|
|
model.
|
|
</Lede>
|
|
<XStack gap={16} flexWrap="wrap" justify="center">
|
|
<Action href="/contact-sales" fill>Talk to sales</Action>
|
|
<Action href="/enterprise">Run it on your own GPUs</Action>
|
|
</XStack>
|
|
</YStack>
|
|
</Band>
|
|
|
|
<Band pad="$10" measure={1152}>
|
|
<Grid columns={{ min: 240, max: 4 }} gap={16}>
|
|
{POINTS.map(([title, body]) => (
|
|
<Leaf key={title} p={24} borderColor="var(--border)">
|
|
<Line render="h3" display="block" mb={8} fontSize="$4" lineHeight="1.4" fontWeight="600" color="var(--foreground)">{title}</Line>
|
|
<Line render="p" display="block" fontSize="$2" lineHeight="1.5" color="var(--muted-foreground)">{body}</Line>
|
|
</Leaf>
|
|
))}
|
|
</Grid>
|
|
</Band>
|
|
|
|
<Band id="deploy" pad="$10" measure={1100}>
|
|
<Head eyebrow="Enterprise deployment" title="On your own premises" lede="What a rack for Zen 6 Max is made of." />
|
|
<Rack ask />
|
|
</Band>
|
|
</Box>
|
|
)
|
|
}
|