It was just timing. Their networking gear was built on some very impressive ASICs which became commodity chips a few years later before they could grow. Arista, Juniper, et al ate their lunch using other vendors’ IP. IIRC it was Broadcom and Fulcrum that released the chips that killed them.
I'm sure there were good reaasons for this, but man this just sounds bad. Like that's the spec I think NSA must give to their contractors outfitting 611 Folsom Street's Room 641A
In my case it was for mobile wireless signaling traffic (all the coordination for creating a mobile internet connection, handing the connection off between towers, etc), and I'd credit it as one of the reasons you're mobile internet connection is so stable. When LTE first came out, myself and many others solved all sorts of bugs in the equipment and protocols by using or building these sorts of tools.
80% of the relevant outcome was typically to get a true-to-the-wire sniffer capture (switch mirrors won't always mirror 100% of packets for various reasons) for troubleshooting performance of whatever the complaint of the day from the server team was.
19% was for feeding a security monitoring systems which looked for abnormal flow patterns to let us know a server was compromised.
1% was for the call recording system compliance requirement for the emergency department.
0% was because I was a cool superspy tasked by the government to siphon info to them or trying to sell medical records on the black market or something. I mean, you can try to something nefarious with such tools... but one could say the same about a generic server, SAN, application, etc as well. People are just used to understanding what those would typically be used for so they don't assume it must be for the scary thing they've heard about.
That said, it doesn't rule it out either. But again, the concern shouldn't be sourcing from their usage of normal infrastructure tools it should be sourcing from... well, all of the user analytics Google very publicly does directly in the server.
https://www.cisa.gov/sites/default/files/2023-02/TLP%20CLEAR...
My home network is XG2000 10G core and a few XG0224 1G/10G dist. Very nice switches.
The same way Congress has been subsidizing Boeing and its competitors since WW2 to make sure we can build things that fly if another war ever starts. Or with drones, that we can build ones that will be flown BY US instead of defecting the moment they get in range of the other side.
Funny you should mention that. Boeing deliberately buys 35% of a 787's airframe from Japan (along with other equipment for the 787 and other models).
That's a deliberate play: we buy a lot of parts from Japanese companies, your airlines buy mostly Boeing airplanes. Even today despite some diversification Boeing has over 70% marketshare in Japan.
If you ever wondered why Airbus setup factories in the USA that's a similar deal. The US Gov and Mil want to ensure factories and workforce on home soil should the need arise. In some unrecorded meetings somewhere strong hints were no doubt dropped that it would be in Airbus' best interest to play ball. They obliged.
That said the USA is the largest supplier of parts for Airbus airliners so there's also a benefit to having aerospace manufacturing and R&D here.
This is the first time ever I am hearing of Fujitsu being involved in any bribing/lobbying controversy in the US (whether as a victim or an offender), and I doubt I am the only user in this thread in this position.
Unless it is a very well-known controversy, I feel like there is a need for extra context here. I am not even asking for anything of the "proof beyond any reasonable doubt" nature, I simply want to understand what you are trying to reference.
Its a genuinely terrible place to do business, and its full of genuinely terrible people to do business with.
Oh and Trump made it a bit worse with Tariffs I guess.
Hope this helps.
wccftech summary: https://wccftech.com/fujitsus-monaka-chip-3d-stacks-2nm-cpu-...
2026: https://global.fujitsu/-/media/Project/Fujitsu/Fujitsu-HQ/te...
2023: https://global.fujitsu/-/media/Project/Fujitsu/Fujitsu-HQ/te...
FugakuNEXT, the supercomputer it will be used in, also some details about the next-gen Monaka-X: https://global.fujitsu/-/media/Project/Fujitsu/Fujitsu-HQ/te...
For a single CPU: 844 GB/s memory bandwidth (12 channels of DDR5 RDIMM, 8800MT/s). 4.3-6 TFLOPS.
Basically comparable to a modern (although not top-end) GPU, so good for HPC & AI workloads. (though only 2 CPUs per node, with GPUs 4-8 is more common)
>Combined with SVE2 vector operations and software optimization,
It’s ARMv9.
Nowadays if you have the source code the ISA is practically irrelevant.
> FUJITSU-MONAKA is a Next-Gen Arm-based processor, set for release in 2027, designed to address the challenges of next-generation data centers with its unmatched performance and power efficiency.
https://global.fujitsu/en-global/technology/research/fujitsu...
It is no secret it is Arm; MONAKA was announced in late 2024.
https://www.techpowerup.com/329761/fujitsu-previews-monaka-1...
>next-generation CPU, FUJITSU-MONAKA [1], designed and developed in Japan
>Fujitsu MONAKA Server, powered by the FUJITSU-MONAKA CPU, enhances sovereign capabilities through domestic manufacturing,
https://en.wikipedia.org/wiki/Japan_Advanced_Semiconductor_M...
>The Phase 2 factory was under construction as of January 2025, next to the Phase 1 facility, and is expected to be completed by 2027.[3] Initially planned for manufacturing semiconductors using a 6 nm process, 3 nm was incorporated into production plans for 2028 in 2026
> Achieving world-class AI inference performance through Japan-developed 2nm 3D-stacked CPU and server integrated, developed, and manufactured in Japan
Sounds pretty clear to me
All the component chips are made at TSMC, in various processes.
"Developed in Japan" means the same thing like "developed in USA" means for NVIDIA or AMD or Intel. You can design chips anywhere on the planet, as long as TSMC is willing to provide you the required documentation and EDA libraries (which it does only if you already are or they believe that you will be a big customer).
Since that theory began to be used, anyone outside US has become anxious to become "sovereign", i.e. to stop using anything about which a foreign state can claim to have rights.
The AI stuff is basically "well sure, these are really good at distributed matrix math, why not?" hoping to get better volumes and make the program cheaper internally.
And they're working on getting chips fabbed in Japan too now that IBM sold their 2nm process to Rapidus, but that's probably successor to these. Maybe 2028? In the meantime there's still more nuclear simulations to run than there is compute to run them.
Michael Palmer, in his book Hiroshima revisited, doesn't go as far as to rule out “nukes” entirely, but damage assessment, medical evidence, witness reports and measurements show that no such thing as claimed by the US and Japanese governments happened in Hiroshima and Nagasaki. Instead, there were other ingredients to the atrocities, like the usual napalm, so-called “pumpkin bombs” (the iconic Nagasaki model), flash bombs and coloured smoke (“special effects”), and mustard gas (to generate “radiation sickness”), which is a gel that can linger on and emit poison for weeks (depending on the weather).
Napalm and mustard gas are 100 % consistent with the medical record, which the author is professionally qualified to assess, citing academic literature (which is scarse in case of napalm, probably on account of its heavy use by the US against East Asian peoples in the “defense of democracy”).
The damage pattern is extensive rather than intensive (that is the military expert assessment), just as seen in other napalmed cities in Japan. Miraculous survivors at the alleged “ground zero” (no such thing can really be derived from the damage pattern) preclude any generation of heat drastically higher than what is attainable by conventional means (“victims were vaporized”). So do slender objects like antennas and trees (which blossomed again next spring, then interpreted as a “miracle”). The few stone buildings there were can be seen standing out among the remains of flimsy huts that were blown and burnt.
And of course there was no disruption in settlement, the cities were built up and inhabited again.
« simulations on what happens with your aging asrenal » — Swarms of red herrings to keep the myth alive. Surely other uses of supercomputers are conceivable, even for non-disclosed purposes.
Strangely, while the non-existence of such weapons is undoubtedly good news, there are many “nuke fanboys” (no girls, though – this is a male thing) who will get upset and even angry at this, as if the “atomic bomb” were some kind of god to venerate, when it really only is lies and propaganda that we've been fed when we were kids.
To be clear, this is not to dispute nuclear energy, just the claim that it may be used to obtain explosions, and even extraordinary ones.
Wafers rare Earth's, specialized equipment, etc?
I don't think it is that basic. If anything it's probably more about having protection from trade and sanction threats, and insulation from shortages, supply chain problems.
> Nothing about this changes that IMO. They're still getting the chips fabbed somewhere else and run the same risks.
It certainly changes it. Chip design is of enormous importance and the technology leaders there are concentrated in the USA.
Silicon manufacturing is a different thing. Japan is also trying to bring up sovereign leading(ish) edge manufacturing. Obviously you keep peeling the onion on everything though - to do digital logic they need EDA tools and quite possibly IP blocks for PCI and DDR and so on. To do manufacturing they need scanners from ASML and a process design from IBM and so on... It doesn't mean that because they can't do everything from the ground up that it's pointless. At some point they need to import coal and iron ore and bauxite.
((2nm 3d stacked CPU) and server) (integrated, developed, and manufactured in Japan)
or
(2nm 3d stacked CPU) and (server integrated, developed, and manufactured in Japan)
That manufacturing step may change in the future, but right now that CPU is not "Made in Japan", it's only "Designed in Japan".
The core die is made with TSMC-N2P, while the SRAM die and the peripheral die are made with TSMC-N5.
Their CPU is designed in Japan, like the AMD CPUs or the Intel CPUs are designed in USA (the latest Panther Lake Intel CPUs have returned for fabrication to USA in 2026, but they also cost double than the corresponding Arrow Lake models made at TSMC in 2025, and their GPUs are still made at TSMC).
Why does this matter? Markets outside the US account for about half of many US technology vendors' revenue. Who is going to speak up first?
Its ARM predecessor started in 2014: https://en.wikipedia.org/wiki/Fugaku_(supercomputer)
And before that they were the using SPARC64: https://en.wikipedia.org/wiki/SPARC64_V
I do find it funny how the harder some folks push for an outcome, the more they bring about the opposite effect.
I mean the US had this sense of confidence that they were at the top of the power structure, it was widely accepted and overall that position and deal seemed to benefit many others even if not to the same scale. For example with Europe, the US got favorable trade terms in exchange for defense.
Then the Trump administration came in and started pushing the narrative of MAGA, to almost be professional victims. Winner of the world lottery and yet still not happy. And so instead of making America Great again, they are on the fast track of being cut out of favorable global trade. They over played their hand. And once others end up being self sufficient again, it is very difficult to get back in the good books.
In trying to avoid being pushed around, they are now starting to see they could be pushed around.
Those questions didn't used to be significant factors.
It's weird that they don't give out any of the interesting numbers like number of memory channels, how much SRAM they have (CPUs tend to have more of it) or what their expected performance is going to be.
See e.g.:
https://chipsandcheese.com/p/hot-chips-2026-fujitsus-monaka-...
They have provided far more details than companies like Apple or Qualcomm.
Edit: it’s funny because this article from 2021 mentioned Fujisu precisely https://siliconangle.com/2021/03/30/arm-unveils-armv9-archit...
It is a custom Armv9.3-A design (same ISA like the Arm C1 CPUs from the flagship smartphones of 2026), but it has double-width execution units for SVE2 (i.e. 256-bit width, vs. 128-bit for the other Arm CPUs) and it has some ISA extensions for AI/ML, e.g. instructions for inference with FP8 (BF16 is already supported by the standard Arm ISA).
Despite the fact that Armv9.3-A may include SME (scalable matrix extension, like in the Apple CPUs and in the Arm C1 CPUs), Fujitsu did not mention SME, so I assume that they did not implement it and they rely on their enhanced SVE2 (which is not surprising, while the origin of Arm SME is at Apple, the origin of Arm SVE is at Fujitsu).
(I think Japanese sovereignty is the main point of the article.)
Seems they have decided they don’t want to create their own architecture, but take the popular architecture and build on it.
See: - Blue LEDs - Quartz Watches - Lithium-ion Batteries - Bidets
The industry is now mature enough that nobody really wants the headache of a new architecture at this point in time, Risc-V got a pass for being a grassroots movement growing out off FPGA's since the IP situation was more or less clear or even predatory with all existing architectures, Power, Sparc,SuperH,68k,etc are buried for good reasons.
POWER/PowerPC is what happens when you take a brilliant design to execute it poorly. x86 is when you take a poor design and execute is brilliantly.
Edit I think I was thinking of Mitsubishi.
About a month later there was a summer heat wave and I went to a friends house who had just bought one. It was wild walking in from a 45c day into, as advertised, a 17c house. Had to give it to them, they lived up to the claim.
That they come from the telecom/server space, it makes sense they had a good eye for aircon engineering.
During the decade 1995-2005, until the 64-bit AMD Opteron servers with Linux offered an alternative that crushed any kind of SPARC CPU with Solaris by a much higher performance combined with a much lower price, the SPARC Sun or Fujitsu servers dominated the market for servers used to host the CAD/EDA design tools used in electronics engineering, for the design of integrated circuits or electronic equipment. This means that all the EDA software from vendors like Mentor, Cadence, Synopsis etc. was available only for Solaris. That kind of software could not be run on Windows, due to the 32-bit memory limit. During that time, whoever got Fujitsu servers instead of the sluggish Sun servers, was very lucky.
In the mid-2000's, Sun decided to take SPARC towards designs with many small SMT cores. In the era of single-core processors, the UltraSPARC T1 had 8 cores x 4 threads per core. This was at the same time Intel released the Pentium 4 with hyper-threading, so it was an industry trend.
This of course works great for very specific applications, particularly considering efficiency, but is awful for others. Scientific computation was especially bad because the T1 had only one FPU for 8 cores.
Fujitsu's SPARC64 didn't go in this direction, and stayed with a conventional design (2 way SMT at most). Sun realized this and started to also sell the Fujitsu SPARC64 for customers who couldn't use the thread level parallelism, an arrangement that lasted until the end.
The idea of lots of slow cores is still a thing today: Intel's Sierra Forest Xeon is 144 E-cores.
Still, iirc FPU's were silicon heavy back in those days and it'd be interesting to know how far ahead the foundries Sun and Fujitsu were, maybe it was simply a factor of being too far behind in the foundry race that left Sun with few options.
Intel's E-Cores still are functionally complete for most parts though (excl Avx512?)? Todays limits seems to be memory bandwidth and power and I guess many of the 144 core customers are in it for virtualization and servers?
What are the GPU capabilities?
Platform designers can make up their own memory maps, so non-x86 ones can just have UART I/O buffer and hardware interface wired up in whatever address you want and forgo VGA.
I have a 32bit SPARC machine on a shelf I got from a junk hardware shop, it has a DB25 for console. It's ok.
Obviously they can just ignore the license in the future and continue development out of a local branch, but it's also a bit disingenuous to speak of "sovereign infrastructure" and then use licensed processor design.
https://en.wikipedia.org/wiki/Monaka
It's not terribly popular even in Japan, since it's dry, bland, fragile and has to be assembled on the spot or it goes soggy.
Pun intended?
Also odd how big an emphasis they put on AI inference when they don't build the GPU?
> For FUJITSU-MONAKA, the 2nm semiconductors will tape out next year. Due to this, Rapidus would be unable to meet the deadline, so TSMC is handling the manufacturing.
Source: https://global.fujitsu/en-global/pr/news/2026/02/12-01?utm_s...
According to Rapidus webpage, they are explicitly starting mass production of their 2nm in 2027.
Source: https://www.rapidus.inc/en/iim/?utm_source=chatgpt.com
Fujitsu has added some ISA extensions for AI inference to the standard Arm ISA, e.g. instructions for inference with FP8.
Even their previous CPU generation was for some time the champion in energy efficiency, with better performance per watt than the NVIDIA GPUs, until a newer generation of NVIDIA GPUs has leapfrogged them.
There are good chances that this new Fujitsu CPU might be again for some time the CPU with the best energy efficiency, but it remains to be seen how it compares with the recent GPUs.
GPU in AI world is essentially a set of specific matrix calculations that this CPU supports on hardware-level. Thought memory speed seems low.
- Japan-developed 2nm 3D-stacked CPU
- server integrated, developed, and manufactured in Japan
so its as sovereign as you can get
like:
- home.kpmg - global.honda
and probably more I forgot about
but as you can see, they're pretty terrible for replacing .com domains
I know that for GPU's the model weights have to be transferred over the bus initially, but that only has to occur once for inference use cases, so is the Fujitsu system more about training scenarios? Or is the focus more about efficiency, as these are ARM-based cores with AI additions?
It's an overcrowded market. Far better would be to focus on semiconductor supply chain, which Japan already supplies some elements, to sell to fabs.
Because the bottleneck is the fabs. If a new 2 nm fab came online today, it would immediately sell all its capacity to 2030 no problem, without Fujitsu trying this gambit.
It's not 'sovereign', the architecture is not designed in Japan, the silicon is not fabbed in Japan. This whole thing is sideways.
The text says "next-generation CPU, FUJITSU-MONAKA, designed and developed in Japan".
Doesn't matter. You have to start somewhere and this is a good start.
So there's a good chance that it's still an optimized half-SPARC inside.
You have been convinced by fake news, please recheck this claim, its false.
> wealthy people
*rich people
> All they know how to do is tax people
Oh god you're one of those. People who complain about taxes have historically been on the wrong side of arguments.
Oh you're one of those. The arrogance is astounding. You never been a country which overly taxes it's citizens and squanders the gains on bureaucracy and monetary black holes? Grow up, your ideological blind spots are making you look like a fool.
And here's more technical information about this generation: https://news.ycombinator.com/item?id=49443040
Kudos to Japan
Fujitsu MONAKA Server will be
made broadly available from
November 2026 to data center
operators, enterprises, and
the academic and HPC sectors
in Japan and Europe, as well
as to the defense sector,
contributing to national
security.
So, not in America. A sign of the geopolitical times? If so, a very unusual one to come out of Japan.There is a fairly direct link between the two numbers. You can predict the latter from former reasonably well
You have to run inference on the GPU by reading and writing to VRAM. So TFLOPS of the compute matters, and bandwidth to the VRAM (Always integrated with the GPU, rarely a bottleneck), and this strongly affects tokens/s
If you're doing training workloads or offloading to system RAM, it gets more complicated. (And mostly bound up trying to feed compute on time)
(Edits for clarity.)
On dedicated inference hardware I'd expect model weights to never leave the RAM, and you'd probably load them on startup before even starting to serve requests
I do find it odd that the 2U model has less storage capacity than the 1U on their chart. That doesn't make much sense to me.
The only fujitsu laptops I used was back in 2011- it was a budget version for on-call and it was fine..
Sounds like the fans running 100% probably contributed significantly to the issue here. If I had to guess it was likely that the C-States were disabled in BIOS somehow so the CPU clock was running at full tilt the whole time, maybe combined with a bad thermal paste job.
I'm not here to defend Fujitsu but I've had really bad experiences with basically every major laptop brand (Dell: majorly bad coil whine and especially faulty soldered RAM, HP: keys vanishing from the keyboard and very weak hinges that break all the time, Apple: The GPU unsoldering itself and the butterfly keyboard shenanigans).
I don't really know any brand with a flawless track record sadly.
Before anyone brings up Thinkpads, they're trading on a reputation that hasn't been true for over a decade. If you have fond memories of a thinkpad it's most likely that you had it from before 2016, or it's "fine", but certainly not great.
Really miss the transflective display and wish that there were newer devices with such technology
I also liked their Primergy Servers, but never got one for a reasonable price to test it out.
Another thing was the Futro series (e.g. S930) that could be used as opnsense firewall or low budget proxmox host.
Unfortunately it was always hard to obtain the high quality stuff as a consumer and years ago they sold their mainboard section to kontron. So no new Fujitsu Mainboards for now... What a pity.
A Pentium 4 hit 3.8 GHz longer than that ago in 2004, so that's not special. And the estimated price will be $7,000-10,000, which isn't special either since that's about 10x more than it should be.
Hot take: GPUs disrupted the CPU industry to such a degree that CPUs never recovered, and like the k-shaped economy, the current status quo only serves a small fraction of customers. We can and should do better, but sadly we won't. Still, it's good that Fujitsu did this, for the competition if nothing else.
Managed languages runtimes are probably the ones that would be better equipped to take advantage of them, for distributed JIT, GC and asynchronous code.
The Connection Machine style with StarLisp.
Very few devs can write optimal multi-threaded code that explores the single digit count of cores on their laptops or phones already.
However one could argue that FPGAs are already that, and still we come back to a skill issue.
I am also not an expert, cannot make heads or tails about SIMD algorithms, and in what GPUs goes, only traditional shading languages.
Let alone algorithms that on top of that, should take optimal advantage of all available CPUs.
IMHO most concurrency problems don't actually need async behavior, they need higher-order methods and models which behave deterministically by encapsulating async behavior internally.
Another maturing solution is to use SAT solvers to prove that all exceptional behavior and failure modes are handled. I'm hopeful that AI will help with that and allow us to exercise programs fully, rather than rely on unit tests and fuzzing.
Personally I think that the UNIX model of orchestrating small async programs that do one thing well is the only proven mainstream solution. Erlang and Go come really close, but unfortunately we need a hybrid of the two, which doesn't currently exist. The pattern for that is functional core, imperative shell. Which mimics the real world where business logic can be formerly proven correct or constrained by types and categories, then we wire up programs cookie cutter style. That avoids the use of monads (promises/futures in imperative languages), which are the main footguns. The closest language that does that is ClojureScript, whose runtime is analogous to suspending and resuming a coroutine or green thread that makes Lisp calls (although that's a poor fit and I'm sure I'm wrong about it).
But you're right that we don't currently have a language that can recruit multicore CPUs. I used MATLAB/GNU Octave in the past, but think that Julia probably has a brighter future since it can already run on GPU mostly unmodified. I would not try to do it with a mainstream language like C# or Python, or even PHP for that matter. Although some of PHP's multiprocessing metaphors are pretty solid, since they intentionally use processes instead of threads like in Ruby. There the problem is latency introduced by poor process models used by Microsoft and Apple, not something fundamental with spawning processes. Real-time Linux attempts to unify the kernel under one process model to provide deterministic timing, which is hard enough for regular Linux and probably out of reach of the big OS companies, because money can't buy everything.
Very nice overview, also agree with the points that you presented.
Does Fujitsu have extensive expertise in processor development? I don't remember any notable Fujitsu processors.
Although, as irusensei notes, this seems to be an ARMv9 processor.
:D
For AI infrastructure:
:(
Their software is so poor that it caused probably the biggest miscarriage of justice in history. Well that and Fujitsu staff colluding with post office executives to put innocent people in prison rather than admit there was a problem
[1] https://en.wikipedia.org/wiki/International_Computers_Limite...
(Which in no way excuses their utter evil.)
Japan is also extremely weary of getting in the way of US. Software is one of few remaining consumer high tech domains that US leads. Challenging that without a good reason isn't a great idea.
I worked for a Japanese company although in a local office with local management. Through all those layers of protection I got the impression that they suffer from what all corporates suffer from - no software engineers that have made it to the top. Software companies run by people who have no clue.
In the US, for example, I think some people who have a clue or a partial clue have made it up the ladder in some places and therefore although everyone there has their horror stories of idiotic behavior it is probably somewhat better.
If anyone on HN knows (there are several other commenters more deeply steeped in Japanese engineering culture), I would love to know why as well.
This, and the 'rise or climb to the top' is more about seniority and social standing than anything else, especially at large Japanese conglomerates. The result us that there are almost none of the software competencies in senior management, and even if there were those would be software competencies from the 1970' and 1980's who are still leading while being 80 years old. There is also a 'filter' put in place at most organizations which are sufficiently large or diverse, such that middle-management is moved across multiple divisions every two or three years during their career. This is presented as a cross-training/cross-competency, but has an effect of preventing those with the most direct contact to the production staff from building enough localized social capital and systemic capability which would enable changes to the workflow not directly from the top. The middle stays in the middle, and the top gets to keep their seat well past any reasonable capability to adapt to the changing world of business.
This leads to the situation, where if leadership were changing with incoming capacity and points of view, there would be a motive and opportunity to admit to company errors; such as acquiring an international subsidiary which produced a faulty product that directly harmed people, because the newer leadership could say: "Sorry, that was a series of bad decisions, and as new leadership my role is to correct the course of business operations."
However, when the leadership is still the same clique that made the errors in either acquisition, oversight, response to the negative outcomes, then that "Sorry" statement would be a career ending move and result in massive social penalties beyond simply a forced retirement which would have lasting socio-economic impacts on the entire clique's family in every facet of business and later prospects. Combined with the strict social responsibility of a large enough scale of harm could lead to actual, not-figurative, suicide.
So, no, there's not going to be any 'mea culpa' for the direct actions of a foreign subsidiary, because those negative outcomes of those poor decisions are not in the direct social awareness in Japan of those surrounding the entrenched leadership and thus do not impact the daily social standing of that clique to the extent that a formal 'taking responsibility' would.
Instead, there will be very public announcements of improved capability which has the indirect and implied meaning of: "Engineering a way to make a better product will keep that from happening again" without ever directly addressing the existence of the faults. Social and economic uplift to counter any negative pressure in the local social awareness equals a success, not a failure.
In order for Japan to actually become successful at software in the near and medium time-frames, there will need to be a large shift in the work-life balance and internal social structure of new startups. This is beginning to happen in small scale, and to the extent that those newer 'brands' can avoid becoming subsidiaries of the larger established conglomerations will determine the slope to that success.
The groups which can empower and embrace a 'star' network topology inside and among organizations instead of 'waterfall' hierarchy will both; struggle to reach the social equity available through corporate-government-financial integration that is strongly entrenched in the established systems, and will outperform those entrenched systems in terms of real productivity through reliable delivery of improved capacity.
The socio-economic inertia of the giant keiretsu-gaisha are immense, but the geriatric cliff is already here and the nation and it's business cultures are at an 'adapt or cease operations' threshold. It's questionable whether any of the globally well know names will remain operational in their prior fields of production over the next 50 to 100 years without a significant shift in developing a way to build direct connections to capacity and applied skills at every tier of each company.
The 25 to 30 year old employees group in every main workforce is barely a fraction of what it used to be, and handling that small group as if it needs a 'filter' to keep the authority concentrated at the top is a significant risk for these organizations.
Those workers at the start of their career who are looking hard at the work-life balance aspect of employment have an inertia which is at odds with that of the organizational behemoths. Many of them are in a position to be drawn out of the crowded city, embrace a rural lifestyle and remote work without the centralized office and it's toxic overwork for underproduction culture. The rural municipalities are developing stronger incentives to attract this mobility, including relocation assistance and direct support with childcare and family building resources. Some prefectures and town offer up to several years of basic food and housing subsidies, low to zero cost fibre internet; next-generation FLET'S Hikari Cross or NTT's eqivalent 10Gbps in a HOUSE instead of a tiny apartment. The major central large conglomerates are going to find that the local in-office work pool will stagnate as the most capable and best informed no longer flow in directly from university and fill every available desk from a waiting list.
The "bigs" have insulated the ledger books with massive foreign investments, so they have the capability to stay 'in-the-game' for quite some time, so long as those investments continue to be productive, but the hollowing out of the main offices in Tokyo is pretty much guaranteed in the next two generations as rural Japan's liveability and economics for raising a family continue to grow, because the 80+ hour workweek labor staff in the city has no incentive to pair up and have kids, and the kids who are graduating in this and the next generation's rural school graduates are less and less likely to stay in the city after university if they want a family.
It's pretty much Japan's only way out of the population crisis that is still worsening. So, either they will adjust and become a productive, blended high tech semi-rural powerhouse without the high stress office culture that developed in postwar recovery, or they risk becoming a history lesson about over-concentration of inflexible management culture and loss of productivity.
The third option: succeed AND keep hyper-concentrated power is dependent on the types of moves that Fujitsu et al. are making today, find a way to automate more and more capacity via Machine Learning and robotics in the hopes of not actually needing an influx of skilled workforce for production.
If this 'hail Mary' play actually were to succeed it only cements a productive income for the shrinking population without resolving any of the causes of that shrinkage, i.e. the population still works 80+ hours a week in a socially disconnected state that in antithetic for raising healthy youthful progeny.
Taken to an 'in extremis' view: Within another 60 to 80 years, this might result in a well funded country of the elderly being waited on by robot butlers with until there is no one left to be waited on or fed the produce grown in automated fields.
I think that he most likely path will be a mixture of all three, in varying measure and with an array of outcomes. We live in interesting times indeed.