Astralis

Company: Astralis

Self-reported purpose: A 3D space learning app that allows users to explore the solar system, planets, missions, stars, and black holes through an interactive experience.

Key claim: To turn the universe into a classroom you can explore.

What changed: The project is a hackathon submission (Devpost entry for OpenAI 2026 hackathon). It represents an early-stage prototype with no evidence of revenue, customers or product-market fit.

Single most important open question: Is there a viable commercial path beyond the hackathon demo, and does the team have a plan to scale beyond a proof-of-concept?

The description states that Astralis is a 3D space learning app built with React, TypeScript, Three.js, and other web technologies. It allows users to:

• Move through the Solar System
• Inspect planets
• Follow orbits
• Control time
• Explore missions
• View planetary interiors
• Ask an AI guide questions about what they see

It also includes Sky Mode, Stars Explorer, and a Black Hole mode.

The app is described as a single, integrated product that connects different modes of exploration without feeling disconnected. The team built it using tools like Codex for faster iteration, and focused on 3D scenes, camera movement, performance, and interactions.

Evidence: Self-reported by the authors.

Confidence: Low — no independent verification or user data.

The author states that Astralis was built because most space apps feel either too basic or too technical, and they wanted something you could actually explore, not just read.

The tagline is: “Astralis turns the universe into a classroom you can explore.”

This positions the product as an educational tool for astronomy with a strong emphasis on interactivity and immersive experience. The claim is that it bridges the gap between simple space apps and overly technical tools by offering a user-friendly, exploratory interface.

The long-term goal, according to the authors, is to turn Astralis into a full platform for learning astronomy through exploration, suggesting an evolution from a prototype to a more comprehensive product.

Evidence: Self-reported.

Confidence: Low — no evidence of market positioning or user feedback.

The description does not state the target customer or ICP (Ideal Customer Profile) explicitly.

However, based on the app’s nature as a 3D educational tool for astronomy, it is likely aimed at:

• Students and educators
• Science enthusiasts
• Learners interested in space and planetary science

There is no indication of specific demographics, usage scenarios, or customer segments beyond general interest in space education.

Evidence: Inferred from product description.

Confidence: Low — no evidence of target customer definition or segmentation.

The project description does not mention any business model, pricing, or monetization strategy.

It is unclear whether the app will be:

• Freemium
• Subscription-based
• Paid one-time purchase
• B2B (e.g., schools, museums)
• B2C (individual learners)

There is no evidence of revenue streams, pricing tiers, or monetization plans beyond the hackathon demo.

Evidence: Not evidenced.

Confidence: Very low — no commercial strategy described.

The team used:

• React
• TypeScript
• Three.js
• React Three Fiber
• Zustand
• Tailwind CSS
• Codex

They also mention:

• Building 3D scenes
• Camera movement and performance optimization
• Handling large-scale data (e.g., planetary distances)
• Interactions between modes

The team notes that they spent significant time on:

• Camera movement
• Performance
• Labels
• Transitions between modes

This suggests a technical focus on user experience, 3D rendering, and interactivity.

Evidence: Self-reported.

Confidence: Medium — the tech stack is detailed, but no delivery or scalability data.

The project is described as a hackathon submission, submitted to the OpenAI 2026 hackathon on Devpost.

There is no evidence of traction, such as:

• Users
• Revenue
• Customers
• Product-market fit
• Adoption metrics
• Iteration history or product development beyond the demo

The authors describe it as a proof-of-concept and mention future plans, but no data supports current usage or impact.

Evidence: Not evidenced.

Confidence: Very low — no traction or maturity indicators.

The description does not provide any information about:

• Competitors
• Market landscape
• Existing players in the 3D space education or astronomy learning space

It is unclear whether there are existing tools or platforms that offer similar experiences, nor how Astralis would differentiate itself.

Evidence: Not evidenced.

Confidence: Very low — no competitive analysis provided.

• No commercialization plan: No mention of pricing, monetization, or business model.
• Low traction: The project is a hackathon demo with no evidence of adoption or user feedback.
• Unproven market demand: No indication that there’s a real need for this product beyond the prototype.
• Limited team size: Only two members, which may limit execution and scalability.
• Technical complexity without validation: 3D rendering and performance are complex; no evidence of how they’ve addressed these at scale.
• No user data or feedback: The app is described as a demo, not a product in use.

Evidence: Inferred from lack of evidence.

Confidence: Medium — based on absence of key signals.

1. What is the intended business model for Astralis? How do you plan to monetize it?
2. Who are your target users, and how did you identify them?
3. Have you tested the app with real users or educators? What feedback have you received?
4. What are the key technical challenges you've faced in scaling the 3D experience?
5. How do you plan to expand beyond the current features (e.g., missions, stars, black holes)?
6. What is your roadmap for product development and user engagement?
7. Are there any partnerships or integrations with schools, museums, or educational platforms?
8. Do you have a plan to build a sustainable team or raise funding?