Starkcom Global is a startup built for a purpose. We want to connect the unconnected and offer telemetry to those who need it the most.
This CubeSat technology is mainly possible because we utilize not just a new computing method (signal computing) as our core paradigm, but we compress network packets. Data compression for signal processing allows for more cost effective rates.
We utilize weather proofing coating for the electronics, so weather is not a problem.
Helikites or Aerostats (the balloon needing to lift these tethered systems) are made of a special material that is extremely durable and meant to hold hydrogen and helium for years.
When the balloons come down due to depreciation, it is usually a process that happens over few days, and that release mechanism happens traditionally within 4 to 5 years. At that point, you have the option to just refill the balloon for safe redeployment.
You are talking about 5000ft above surface levels (sometimes slightly above 4000ft from a high rise building or structure), and based off of technology that minimizes safety risks. Instead of satellites that have a 5 year shelf life maximum, you have the option to simply refill with helium rather than buying satellite after satellite and worrying about space debris or large scale launches with rockets/ballistics.
The data compression we use has one of the highest compression ratios in the market, and data is already available for our data compression.
Advanced software like proxy monitoring, Kafka, and scalable databases allow us to monitor user accounts, and uptime.
We utilize various software for connectivity options which include free5gc (free5gc.org), ESP32, SMESH, the Decentralized-Internet SDK, and Hybrid Mesh for mobile connectivity, WLAN, LoRa, MQTT, and Particle.io Thread Options.
This means you can have mobile networks (GSM, Phones, Tablets), IoT devices (Particle.io, WIO Link, Raspberry Pi, Arduino), Mesh Networks (Industrial Automation, Offline Emergency Alerts), Radio Networks (LoRa), and Hybrid Networks (Data Sharding, Tor) all connected.
Besides the software options, we have our unique Stark Compute Module that can act as a terminal/gateway. We also can work with spectrum licensing and related entities to rend IP Blocks or Proxies to be able to be part of the global TCP/IP and WLAN routing systems.
We can be profitable while costing substantially less than many competitors out there. This is because they use legacy methods over a hybrid approach. Better math in should lead to better margins. Our goal isn't to be as expensive as we can be, but offer aide, connectivity, and power to our brothers, while still being able to maintain extremely decent profits.
The compute module we have is the Stark Compute Module. The beauty of the Stark Compute Module is that it is already patented. You know how the circuits look, and we are as transparent as possible without revealing too much about the secret sauce in the software side.
You can go online and search the patents, and we even have some open source telemetry protocols such as the Decentralized-Internet SDK. Our level of transparency is unprecedented because we are researchers, who are serious about changing the game.
Our engineers have research history. This includes the founder having citations from top institutions, including the EU, and a blockchain architect on the team who was a top ranked student nationally along with an ex-Tesla/Nintendo/Bankjoy engineer working on StarkMaps/Prychat. Joe Mansy, our planned project engineer in the US is already doing experimentation on ignition sensors for a startup founded by his own cousin. We speak the language of mathematics and hardware.
Our limitations for a company founded in 2018 (whose history dates back prior) has been narrowed to two core issues #1 Politics, and #2 Regulations. Powerful people rather spend millions of dollars lobbying against a disruptive piece of technology, copycatting us with a worse version, or creating regulatory hurdles rather than allowing us to compete fairly here in the states. We are transparent about that. This is why we have advisors to help us strategically cross-border.
What is different between Starkcom and Project Loon? We have different design, architecture and telemetry choices all together. The main similarity with Google's Project Loon is that they use Aerostats (as we use custom Helikites) to deploy. We also treat our balloons with Ultra/Super High Float and use coating to protect the electronics.
What CubeSat deployment mechanism does Project Loon use as opposed to Starkcom? Project Loon is more focused on swarm communication at the LEO level, we are at this time more focused on stationary points and lower elevation.
What transmission and architecture method do you use as opposed to Project Loon? We utilize WANET + Direct to Terminal Gateway, Loon however utilizes strictly specialized Electro-optical transmission.
How do you compare to Starlink? We utilize Radiosonic communication and standard software defined networking, as well as a low power transceiver module focused on local frequencies over global. Starlink has intelligence tracking similar to ORBCOMM, higher Ku-band range, and utilizes optical multiplexing. We too integrate rerouting and multiplexing for signaling.
Do you plan on integrating intelligence tracking and higher transmission capabilities in the near future? In the near future, we would utilize GPS and timestamping for intelligence tracking through path tracking, and can utilize high power, longer range components. For the low elevation stationary design, there is no need to do that.
