Star Citizen development history in 2012 and 2013 begins with a company milestone and an early campaign record. This section focuses on those documented starting points, not the game’s full development history. Learn more in When Did Star Citizen Start Development?
That narrow view helps you separate what was recorded early from what happened later. The timeline notes the creation of Cloud Imperium Services, LLC, while the official funding-goals page captures campaign ambitions; together, they offer a snapshot of the project’s opening period. [1][2]
Two records, two kinds of milestone
The company timeline and the campaign page tell different parts of the story. One records a corporate milestone; the other describes intended project scope through funding goals. [1][2] Keeping those records distinct makes it easier to read an early timeline without treating company events and campaign promises as the same kind of development progress.
For example, a company entry tells you about the organization, while a funding-goals entry tells you what the campaign presented as a goal. Neither type of entry, by itself, supplies a complete account of how the game developed afterward. [1][2]
Keep the timeframe narrow
This overview stays with the early company and campaign records rather than stretching into later development. The timeline excerpt documents a company event in 2012, and the campaign page captures an early set of goals; these are useful markers, not a year-by-year account of everything that followed. [1][2]
That distinction matters when you read dates or goals in context. Treat them as evidence of what was recorded or planned at that point, not as proof of later outcomes. The focus here is the opening chapter: the early organizational record and the ambitions visible in the campaign, without turning this snapshot into a complete development history.
What began in 2012?
The timeline dates Cloud Imperium Services, LLC’s creation to April 9, 2012, and describes its name as generic and non-descriptive before a later renaming. [1] That is a specific company milestone, not a complete account of Star Citizen’s public history. It also helps to read Star Citizen History Before Release: Key Milestones.
A company date, not the whole project story
When you read “created” in this timeline, keep the claim narrow: it refers to the formation of the named company. It does not, by itself, tell you when the project was first discussed publicly, what players had seen, or how development unfolded beyond that entry.
That distinction matters when you compare different kinds of historical records. A company timeline tracks organizational events; a project history may include public announcements, campaign activity, and conversations about the game. Treat those as separate threads unless a record explicitly connects them.
What the generic name tells you
The timeline characterizes “Cloud Imperium Services, LLC” as a generic, non-descriptive name and notes that it would be renamed later. [1] For a reader tracing the project’s beginnings, this is useful as an early naming detail, but it should not be stretched into a claim about the company’s plans or the game’s design.
For example, if you are building a personal timeline, place this entry under company formation and label it with the name used at that point. Keep public-facing project milestones in their own entries, rather than assuming the company’s creation marks the project’s first public appearance.
How to use this milestone
Use April 9, 2012, as the date attached to the company entry, and retain the distinction between the company and the broader project. [1] If you encounter other early records, compare what each one actually documents: legal or organizational naming belongs in one category, while public discussion belongs in another.
This approach keeps the timeline useful without asking one company entry to stand in for a much wider history. It also makes it easier to spot what a record establishes—and to avoid treating a narrow administrative detail as a complete account of Star Citizen’s early public life. To go further, see Star Citizen Open Development: How It Works.
How did the early campaign shape the project?
Early campaign goals show that Star Citizen’s planned scope included an additional playable ship class—the cruiser—and that all Kickstarter goals were unlocked. [2] Read those goals as a statement of intended scope, not as a promise that every feature would arrive immediately.
What the cruiser goal tells you
The cruiser goal points to an ambition beyond adding another individual ship: the campaign described an additional playable ship class. [2] In practical terms, a ship class signals a category in the game’s planned roster, while a particular ship is one example within that category. The page names the cruiser, but this brief entry does not spell out its gameplay role or explain how players would use it.
That distinction helps you read campaign language carefully. A goal can tell you what the project aimed to include, but it does not by itself give you a delivery date, explain implementation details, or show when a feature became playable. For example, seeing “cruiser” among the goals is a reason to recognize the intended scope—not to assume that you could fly one as soon as the campaign goal was reached.
How to interpret “all goals unlocked”
The funding-goals page states that all Kickstarter goals were unlocked. [2] That records the campaign’s funding-goal status, but “unlocked” should not be confused with “immediately delivered.” If you are tracing the project’s development, treat campaign goals as plans and milestones in the campaign narrative, rather than as a complete schedule of finished game features.
This is a useful distinction for any backer-facing feature list. A listed goal can shape expectations about the project’s direction while leaving questions of timing and implementation unanswered. For instance, you can note that the cruiser was part of the intended playable roster without inferring when it would enter the game or what systems it would require.
The clearest takeaway is to separate scope from delivery: campaign goals document what the project set out to include, while the goals alone do not establish when each item would be available. That keeps the early history grounded in what the campaign page actually records, without turning an ambition into a claim about an immediate release.
How should you read this early timeline?
Read 2012–2013 as a bounded early-development period, not as a complete timeline of Star Citizen’s creation. The documented points available for this section anchor that period in 2012; they do not provide a sequence of milestones for 2013. [1][2] For a closer look, read Star Citizen in 2012–2013: Early Development and Podcasts.
Keep different kinds of milestones separate
A company record and a campaign goal describe different things. The development timeline records a company-formation event, while the funding-goals page describes a planned game feature and the campaign’s goals. [1][2] When you read them, keep the business timeline and the project’s intended scope in separate mental columns rather than treating them as consecutive production updates.
For example, a company milestone tells you about the organization at a particular point; it does not, by itself, tell you that a particular game feature was built or released then. Likewise, a campaign goal describes what the project said it would include, not a dated report that development had completed that work. The page says an additional playable ship class, the cruiser, would feature in Star Citizen and that all Kickstarter goals were unlocked. [2]
Treat the date range as a limit
The label “2012–2013” sets the intended scope, but it should not lead you to fill gaps with assumed events. The timeline excerpt gives a specific 2012 date, and the funding-goals excerpt refers to a 2012 cutoff; neither excerpt gives a dated 2013 development milestone. [1][2] So if you are building your own notes, record only the dated events you can place, and leave 2013 without an invented entry.
This approach also makes comparisons clearer. If a later account discusses a feature’s completion or a production change, treat that as a later event unless it is explicitly dated to this early period. For a compact timeline, label each entry by what it documents—company, campaign, or development—so a goal does not accidentally become a claim about delivery.
What do 2012 and 2013 tell you about the project?
These early milestones show both a concrete company step and the scale of the ambitions attached to Star Citizen’s campaign. The development timeline records Cloud Imperium Services, LLC being created in 2012, while the campaign goals describe a planned additional playable ship class: the cruiser. [1][2]
The useful takeaway is to read those goals as a picture of intended scope, not as a checklist of what players could immediately use. For example, seeing “cruiser” in a campaign goal tells you the project aimed to include that ship class; it does not, by itself, tell you when it would become playable. [2] That distinction helps you understand the early project without treating a promise or goal as a delivery report.
Together, the company milestone and campaign goals offer a narrow but useful view: one marks an organizational step, and the other captures an ambition for the game. They are an opening chapter in Star Citizen’s development history, not a complete account of everything that followed. To keep the timeline in perspective, read these early events alongside later development coverage rather than using them as a summary of the entire project.