-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
392 lines (375 loc) · 17.3 KB
/
index.html
File metadata and controls
392 lines (375 loc) · 17.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Iridyne — Applied AI Lab</title>
<meta
name="description"
content="Iridyne is a collaboration-first applied AI lab advancing medical multimodal research and developer infrastructure for real-world systems."
/>
<meta property="og:title" content="Iridyne — Collaboration-first Applied AI Lab" />
<meta
property="og:description"
content="Partner with Iridyne on medical multimodal systems and developer infrastructure that move from research to reliable production."
/>
<meta property="og:type" content="website" />
<meta property="og:url" content="https://iridyne.github.io" />
<meta property="og:image" content="https://iridyne.github.io/og-cover.png" />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Iridyne — Collaboration-first Applied AI Lab" />
<meta
name="twitter:description"
content="Build research-backed AI systems with Iridyne: medical multimodal intelligence and engineering infrastructure."
/>
<meta name="twitter:image" content="https://iridyne.github.io/og-cover.png" />
<link rel="stylesheet" href="./styles.css" />
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Iridyne",
"url": "https://iridyne.github.io",
"sameAs": ["https://github.com/iridyne"],
"description": "Collaboration-first applied AI lab focused on medical multimodal systems and developer infrastructure."
}
</script>
</head>
<body>
<div class="fx-layer" aria-hidden="true">
<span class="fx-orb one"></span>
<span class="fx-orb two"></span>
<span class="fx-orb three"></span>
</div>
<div class="fx-grid" aria-hidden="true"></div>
<header class="nav">
<div class="container nav-inner">
<a class="brand" href="#top" aria-label="Iridyne home">
<span class="brand-mark" aria-hidden="true"></span>
<span class="brand-text">Iridyne</span>
</a>
<nav class="nav-links" aria-label="Main navigation">
<a href="#focus">Focus</a>
<a href="#advantage">Advantage</a>
<a href="#social-proof">Social Proof</a>
<a href="#flagship">Flagship</a>
<a href="#case-studies">Cases</a>
<a href="#proof">Proof</a>
<a href="#process">Process</a>
<a href="#collaborate">Collaborate</a>
<a href="#faq">FAQ</a>
<a href="#repos">Repositories</a>
</nav>
</div>
</header>
<main id="top">
<section class="hero">
<div class="container hero-inner">
<div class="reveal on">
<span id="heroKicker" class="kicker"></span>
<h1><span id="heroTitle" class="gradient-text"></span></h1>
<p id="heroCopy" class="hero-copy"></p>
<p id="heroCopyZh" class="hero-copy hero-copy-zh"></p>
<div class="cta-row">
<a id="heroPrimaryCta" class="btn btn-primary" href="https://github.com/iridyne" target="_blank" rel="noreferrer">
Explore Repositories
</a>
<a id="heroSecondaryCta" class="btn btn-secondary" href="#repos">See Showcase</a>
</div>
</div>
<div class="hero-card-wrap reveal on">
<article class="hero-card" id="heroCard">
<div class="hero-card-head">
<h3>Lab Signals</h3>
<span class="hero-dot" aria-hidden="true"></span>
</div>
<div class="metric-grid">
<div class="metric">
<strong id="signalRepoCount">--</strong>
<span>Public repositories</span>
</div>
<div class="metric">
<strong id="signalStarCount">--</strong>
<span>Total stars</span>
</div>
<div class="metric">
<strong id="signalRecentCount">--</strong>
<span>Updated in 90 days</span>
</div>
<div class="metric">
<strong id="signalTopLanguage">--</strong>
<span>Top language</span>
</div>
</div>
</article>
</div>
</div>
</section>
<section id="focus">
<div class="container">
<h2 class="reveal">Focus Areas</h2>
<p class="section-sub reveal">
Iridyne operates at the intersection of applied AI and systems engineering, with two clear tracks for execution.
</p>
<div class="pillars pillars-2">
<article class="panel reveal">
<h3>Medical Multimodal Systems</h3>
<p>
Research-to-implementation workflows for multimodal medical intelligence, emphasizing model fusion,
robustness, and practical usability.
</p>
</article>
<article class="panel reveal">
<h3>Developer Infrastructure</h3>
<p>
Tools and pipelines that improve speed, reproducibility, and quality of engineering work across modern
AI-native teams.
</p>
</article>
</div>
</div>
</section>
<section id="advantage">
<div class="container">
<h2 class="reveal">Why teams choose Iridyne</h2>
<p class="section-sub reveal">
The value is not only model ideas. It is the combination of research depth, engineering discipline, and
collaboration style that helps work survive contact with real constraints.
</p>
<div class="advantage-grid">
<article class="panel reveal">
<h3>Research with delivery pressure</h3>
<p>We care about novelty, but we also design for reproducibility, iteration speed, and eventual deployment.</p>
</article>
<article class="panel reveal">
<h3>Multimodal-first thinking</h3>
<p>We work comfortably across text, vision, speech, and structured signals instead of treating modalities in isolation.</p>
</article>
<article class="panel reveal">
<h3>Low-friction collaboration</h3>
<p>We prefer clear scopes, visible milestones, and direct technical communication over vague consulting theater.</p>
</article>
</div>
</div>
</section>
<section id="social-proof">
<div class="container">
<h2 class="reveal">Social proof that feels technical, not theatrical</h2>
<p class="section-sub reveal">
We prefer evidence over slogans. These collaboration signals reflect how teams describe our working style.
</p>
<div class="social-strip reveal" aria-label="collaboration signal tags">
<span class="signal-pill">Research + Engineering</span>
<span class="signal-pill">Fast Feedback Loops</span>
<span class="signal-pill">Clear Scope Ownership</span>
<span class="signal-pill">Reproducible Delivery</span>
</div>
<div class="testimonial-grid">
<article class="panel reveal quote-card">
<p>
“Iridyne helped us move from fuzzy multimodal ideas to testable architecture decisions in weeks, not
quarters.”
</p>
<span>— Research Lead, Healthcare AI Team</span>
</article>
<article class="panel reveal quote-card">
<p>
“The biggest value was execution clarity: concrete milestones, transparent tradeoffs, and no consultant
fluff.”
</p>
<span>— Engineering Manager, Product Infrastructure</span>
</article>
<article class="panel reveal quote-card">
<p>
“They balance novelty with shipping constraints. That combination is rare and exactly what we needed.”
</p>
<span>— Technical Founder</span>
</article>
</div>
</div>
</section>
<section id="flagship">
<div class="container">
<h2 class="reveal">Flagship Projects</h2>
<p class="section-sub reveal">Representative projects that define current direction and engineering standards.</p>
<div class="repo-grid flagship-grid">
<article class="repo-card show reveal">
<div class="repo-head">
<a class="repo-name" href="https://github.com/iridyne/medfusion" target="_blank" rel="noreferrer">medfusion</a>
<span class="chip">Medical AI</span>
</div>
<p class="case-line"><strong>Problem</strong> Fragmented multimodal clinical signals.</p>
<p class="case-line"><strong>Approach</strong> Fusion-first architecture for robust multimodal reasoning.</p>
<p class="case-line"><strong>Status</strong> Active evolution with production-oriented experiments.</p>
</article>
<article class="repo-card show reveal">
<div class="repo-head">
<a class="repo-name" href="https://github.com/iridyne/cinnabar" target="_blank" rel="noreferrer">cinnabar</a>
<span class="chip">Dev Infra</span>
</div>
<p class="case-line"><strong>Problem</strong> Privacy and latency limits in voice tooling.</p>
<p class="case-line"><strong>Approach</strong> Offline-first speech pipeline with lightweight runtime.</p>
<p class="case-line"><strong>Status</strong> Active optimization for practical local deployment.</p>
</article>
<article class="repo-card show reveal">
<div class="repo-head">
<a class="repo-name" href="https://github.com/iridyne/prism" target="_blank" rel="noreferrer">prism</a>
<span class="chip">Tooling</span>
</div>
<p class="case-line"><strong>Problem</strong> Inconsistent build and iteration workflows.</p>
<p class="case-line"><strong>Approach</strong> Pragmatic tooling layer for repeatable engineering loops.</p>
<p class="case-line"><strong>Status</strong> Actively updated around team execution quality.</p>
</article>
</div>
</div>
</section>
<section id="case-studies">
<div class="container">
<h2 class="reveal">Case snapshots</h2>
<p class="section-sub reveal">
Typical project patterns where collaboration with Iridyne creates measurable movement.
</p>
<div class="case-grid">
<article class="panel reveal case-card">
<h3>Multimodal clinical triage prototype</h3>
<p>
Built a scoped prototype that integrated notes + imaging metadata, established evaluation baselines, and
reduced iteration uncertainty before full-scale build.
</p>
</article>
<article class="panel reveal case-card">
<h3>Internal AI tooling acceleration</h3>
<p>
Redesigned dev workflow around repeatable prompts, evaluation checkpoints, and local tooling loops,
improving experiment throughput and handoff quality.
</p>
</article>
</div>
</div>
</section>
<section id="proof">
<div class="container">
<h2 class="reveal">Proof</h2>
<p class="section-sub reveal">
We prioritize shipping and maintainability over slogans. These signals are fetched directly from public repositories.
</p>
<div class="proof-grid reveal">
<div class="panel">
<h3 id="proofRepoCount">--</h3>
<p>Selected repositories in showcase</p>
</div>
<div class="panel">
<h3 id="proofRecentCount">--</h3>
<p>Repositories updated in 90 days</p>
</div>
<div class="panel">
<h3 id="proofUpdatedRepo">--</h3>
<p>Most recently shipped repository</p>
</div>
<div class="panel">
<h3 id="proofLanguages">--</h3>
<p>Top language in active set</p>
</div>
</div>
</div>
</section>
<section id="process">
<div class="container">
<h2 class="reveal">How collaboration works</h2>
<p class="section-sub reveal">
We keep the engagement model simple: align on the problem, validate quickly, then build with clear checkpoints.
</p>
<div class="process-grid">
<article class="step-card reveal">
<span class="step-index">01</span>
<h3>Scope the problem</h3>
<p>Define target users, constraints, available data, risk boundaries, and what success actually looks like.</p>
</article>
<article class="step-card reveal">
<span class="step-index">02</span>
<h3>Prototype the approach</h3>
<p>Pressure-test architecture choices early with focused experiments instead of committing to a large blind build.</p>
</article>
<article class="step-card reveal">
<span class="step-index">03</span>
<h3>Ship the system</h3>
<p>Turn the validated direction into maintainable code, measurable outputs, and a handoff the team can keep using.</p>
</article>
</div>
</div>
</section>
<section id="collaborate">
<div class="container">
<h2 class="reveal">Collaborate with Iridyne</h2>
<p class="section-sub reveal">
We work with research teams and builders who need rigorous experimentation plus reliable engineering delivery.
</p>
<div class="collab-grid reveal">
<article class="panel">
<h3>Research Collaboration</h3>
<p>Co-develop multimodal methods, benchmark design, and reproducible experiment pipelines.</p>
</article>
<article class="panel">
<h3>Engineering Collaboration</h3>
<p>Build and harden practical AI systems with clear constraints, metrics, and handoff quality.</p>
</article>
<article class="panel">
<h3>Technical Due Diligence</h3>
<p>Audit model, tooling, and workflow decisions to identify weak spots before they become expensive.</p>
</article>
<article class="panel">
<h3>Internal Tooling Acceleration</h3>
<p>Design lean developer systems that reduce friction around iteration, evaluation, and local productivity.</p>
</article>
</div>
<div class="cta-row collab-cta reveal">
<a class="btn btn-primary" href="https://github.com/iridyne" target="_blank" rel="noreferrer">Collaborate on GitHub</a>
<a class="btn btn-secondary" href="#flagship">Review Flagship Work</a>
</div>
</div>
</section>
<section id="faq">
<div class="container">
<h2 class="reveal">FAQ</h2>
<p class="section-sub reveal">
A few quick answers for teams deciding whether the fit is real.
</p>
<div class="faq-list">
<article class="panel reveal">
<h3>What kind of teams are the best fit?</h3>
<p>Research groups, AI product teams, and technical founders who need both experimentation quality and pragmatic execution.</p>
</article>
<article class="panel reveal">
<h3>Do you only work on medical AI?</h3>
<p>Medical multimodal systems are a core strength, but the same engineering discipline also applies to broader AI infrastructure and developer tooling.</p>
</article>
<article class="panel reveal">
<h3>What does a first engagement usually look like?</h3>
<p>Usually a scoped technical collaboration around one concrete system, workflow bottleneck, or research-to-production bridge.</p>
</article>
</div>
</div>
</section>
<section id="repos">
<div class="container">
<div class="repos-head reveal">
<div>
<h2 id="reposTitle"></h2>
<p id="reposSubtitle" class="section-sub"></p>
</div>
<a class="btn btn-secondary" href="https://github.com/iridyne" target="_blank" rel="noreferrer">
View all on GitHub
</a>
</div>
<div id="repoStatus" class="status reveal">Loading repositories from GitHub…</div>
<div id="repoGrid" class="repo-grid"></div>
</div>
</section>
</main>
<a id="stickyCta" class="sticky-cta" href="https://github.com/iridyne" target="_blank" rel="noreferrer">Collaborate</a>
<footer>
<div class="container">© <span id="year"></span> Iridyne · Applied AI Lab</div>
</footer>
<script src="./app.js" defer></script>
</body>
</html>